|The Execute Process action launches an .exe specified by the user, the exit code of the .exe that launches is stored in the resource key defined on this element. This can then be used for comparison later in the assert step.|
Execute Process Editor
|Arguments||Enter in command line arguments to launch this program.|
|Executable||The location of the .exe file you want to execute.|
|Resource Key||User defined key that the exit code of the .exe is stored in.|
|The Load Asset action loads a text file into the resource bag so that it can be used in asserts. This helps to bypass the need of writing the content of the asset to a file before comparing it.|
Load Asset Editor
|Text file asset||The text file asset you want to load.|
|Resource Key||The name of the resource key to assign.|
Read Historical Results
Read Historical Results
|The Read Historical Results actions specifies a past run of an assert, grabs the results, and compares it to a more recent or previous result. This allows you to compare results over time, and keep track of test quality over time.|
Important: The Read Historical Results action only works with test groups that publish their results to the SentryOne Test Web Portal. For more information about server integration, please see the Integrating with the Remote Agent article.
Read Historical Results Editor
|Source Element||Opens a selection dialogue where you select an assert from the test group.|
|Target Resource Key||The name assigned to the result that's stored in the Test Resources.|
|Retrieval Mode||There are three retrieval modes available to choose from:|
|Retrieve result from the most recent test run||This option gets the result from the very last time this assert was run.|
|Retrieve result from a previous test run||This option brings up another option to fill in : |
- Number of Runs - This field determines which run to get, 1 would be the previous run, 2 would be two runs ago and so on.
|Retrieve the result from a test run between two dates/times||This option brings up two new fields :|
Select a start and end time for searching for a result, then the first assert in that time frame is used.
|Default Result Source||The default result source is used when the action isn't able to retrieve an existing assert in the options provided.|
|The Timing End action is used along side the Timing Start action. This actions serves as the endpoint for measuring the number of seconds that have elapsed between the start and end.|
|Timing start point||The starting point to begin timing. This opens a list of available Timing Start actions to choose from.|
|Resource Key||The name given to the number of seconds measured that are stored in the Test Resources.|
|The Timing Start action is used along side of a Timing End action. When the test hits the Timing Start action, it starts counting the number of seconds elapsed, and once the test hits a Timing End action, the number of seconds are then stored in the Test Resources using the Resource Key specified by the Timing End action.|
There is nothing to edit for a Timing Start action. The connection of a start to an end is handled in the Timing End action.
|The XPath Extract action is used with an Execute Report action to extract information from the report. Select the resource key of the report that was previously executed, and then you supply the xpath with the information you want to retrieve. The information extracted is then stored in another resource key that can then be used with one of the assert actions to verify the validity of the data. If multiple nodes are matched, then only the value of the first node returns. If no information is found at the node where the path is directed, you can specify if the test fails or continues.|
|Fail if node not found||Specifies whether or not to fail the test if a node can not be found.|
|Path||The XPath to apply to the XML to retrieve the value.|
|Resource Key||The resource key of the XML.|
|Target Resource Key||The resource key to store the extracted value.|