importResults - import session results from CSV file
importResults.pl [-n] [-v] [-d description] [-V varname=value] -u user -S set | -C | -A sessNum suite csvFile [varFile] importResults.pl [-n] [-v] [-V varname=value] -u user -s sessNum suite csvFile [varFile]
importResults allows the import of qualified records from a CSV file into an existing or new session in an ATM test suite.
In the first form, create a new session from the set "set", optionally providing a description for that session. In the second form, use session "sessNum". Import the results for tests in the session that match records in the csvFile into that session.
Don't do anything - just show what would be done.
Assign the value
value to session variable
varname. You can specify multiple -V options. See also
Create a new session in the set named "set".
Create a new session not affiliated with a test set and populate it with all the tests referenced in the CSV file.
Update session sessNum, but add to it any tests that are in the CSV file but are not already in the session.
Provide a description for the new session.
Put the results into the session "sessNum".
Attribute the run to this ApTest Manager username.
The test suite to import into.
The input file (the first line of which must be the field names).
A two-column CSV file defining session variables that should be set on import. The first column is the variable name, the second is the value.
The csvFile must contain at least the following fields:
The name of a test case that is in the session or, in auto-outlined suites, its outline number.
The result of executing the test. This must be one of the results defined for the suite.
Notes about the execution of the test.
It can also contain the following fields:
The amount of time it took to run the test case (only useful if the test suite SCHEMA includes a stafftime field).
The amount of time it took to run the test case (only useful if the test suite SCHEMA includes a clocktime field).
In addition, it can contain any fields in the suite's run data definition, for example:
The problem report ID for the test.
A link to the problem report in a bug-tracking system.
Any fields that do not match the run data definition, or one of the special fields listed above are ignored.
An example result file might look like:
ID,RESULT,NOTES,ATM_PRID mytestcase,pass,"some notes about this test case",42 myothertestcase,fail,"another test case with notes",43
Copyright © 2000-2013 Applied Testing and Technology, Inc. All rights reserved.