Results are proposed in the form of a table with one line for each macro command and one line for the test result. All lines generated by the task scheduler are mixed in the same table. The filters will permit to select results of a specific task, robot port or whatever depending the filters parameters. The columns of the table reflect the command parameters and results with:
- No: Line number of the command inside a task. Will restart to 1 when a task starts, continue to grow if the task run for a new iteration.
- Time: The time stamp of the line when the corresponding command is sent to the robot or run as analysis by the task processor.
- Task: The task name at origin of the command or “$$ RUN $$” if the command was sent during an immediate macro run from the macro edition dialog.
- Test Name: The test name under execution.
- Iter: The iteration number of the test. 0, if there is no iteration. 1 to N if the test must be ran several times.
- Action: The type of action which generates the line, EXECUTE, ANALYSIS, GET RESULT etc …
- Macro: The macro name if action is EXECUTE
- Data: Name of the data collection used to run the test.
- Robot: Name of the robot that run the command
- Port: Port number of the robot that run the command
- Command: Name of the Command inside a macro or analysis.
- Category: Category of the Command in R2D2 API.
- Input: Constants or variables (from data collection) used as input parameters of the command.
- Output: Output code generated by the command
- Exit: General status return by the R2D2 API if EXECUTE action or exit code if EXIT action, or internal result of the task processor.
- Exit Cause: Exit cause parameter given by EXIT FAIL or EXIT PASS action.
An export button permits to extract the entire table or a filtering result in a CSV file. A delete button opens a dialog to propose several deletion options: - Clear the entire table results - Delete the selected lines. - Delete the selected task results - Delete results between two timestamps See below an example of results table
EXPORT AND IMPORT
Three kinds of objects can be exported and imported in the test manager, the data collection, the macros and the tests.
Each of these objects can be exported one by one as a text file in order to transfer tests from one IRON suite to another.
In the object list of each test manager pane, select objects and click the Export button. A window will propose to save the exported object description as a text file. The name of the exported file is prefixed by the type of object and ended by “itm.txt”. For example we will have macro.SendSMS.itm.txt or data.CalledList.itm.txt.
For the data collection an option will permit to export the data collection structure only or to save also the complete data content.
To import in another IRON suite, you have to select the right pane, data collection, macro or test, click the import button and select the right file.
Importing a test is a little bit more complex because most of the tests include references to other objects like data collections, macros or other tests used as child tests. The import process is designed to relink the cross references in the destination IRON suite. To do that, you must import first the data collection, then the macros, the tests used as child tests and finally the main tests. Taking this precaution will guaranty that when the tests are imported, the references of the included objects are relinked. If an object reference inside a test is broken it will be displayed in red color in the test edit window and the user has to select a new object to relink the broken reference.
The robots and ports of a test have always to be selected when a test is imported due to the fact that list of test robots is specific to each IRON suite.
If a test is run with a broken reference, it will fail with “unresolved dependences” error.