...
| Field | Description |
|---|---|
Configuration Name | Enter a name for your Configuration |
Type | Select the test type from the drop down list. HP Quick Test Professional, IBM Rational Functional Tester,Selenium or Unit Test Results |
Sub-Type | Only applicable for Unit Test Results. Select from the dropdown list the type of results you are importing |
Default Path | If you also plan on manually importing results enter the pathway. Otherwise leave this field blank. |
Source Path | Enter the path to the results file to upload e.g. c:\testdata\{Name}.xml |
Name Template | Enter a name for the results files e.g.{name} |
Combine Results | Check to combine all results in the path into a single run. This can be useful for unit test where there maybe many xml files which comprise of a single run. |
Skip files if unchanged | Check to skip importing files if they have not changed since the last import. e.g. the tests have not run since the last schedule import. |
Root Script Package | Select the package/ folder in the Script Library where you would like the Automated Test Script created. |
Root Execution Package | Select the execution package to import the run results to. |
Retained Max # Results | Enter the maximum number of runs to retain ( in the run history of the automated test assignment). Runs outside of the retention period will be removed. |
Using the Source Path and Name
...
Template
...
Creating a Single Automated Test from a Single File
In its simplest form a schedule can be created to import a single file as a result into an automated test assignment.
| Info | ||
|---|---|---|
| ||
Source Path: c:\testdata\results.xml Name Template: my |
...
result |
Creating an Automated Test from a Folder of Results
...
| Info | |
|---|---|
|
| |
Source Path: c:\testdata\ |
...
my results |
These both behave in the same manor as manually importing an automated test result and filling in the "Results Path" field on screen. In addition, zip zip files are also supported, which effectively works similarly to configuring a folder (with the contents of the zip file treated the same as the contents of the folder).
...
Capturing part of the path into the "name" variable
It is also possible to "capture" part of the path into a special variable called "name" which can then be referenced within the "Name template" to generate a unique name for each test, .
Below is an example using files:
| Info | ||
|---|---|---|
| ||
Source Path: c:\testdata\{name}.xml For a directory of files, here is what would be |
...
generated
|
...
Source Path: c:\testdata\{name}\ Name Template: {name}
|
Wildcards are are also supported. In the Source path, you can replace the name with "*" . Wildcards are are not supported supported in the Name Template field.field
| Info | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Source Path: c:\testdata\*\
|
Limitations
There some limitation so the Source Path and Name Template fields. These include the following:
...
You can use the tool bar to add new import schedules, delete an existing configuration, enable or disable an existing schedule, configure an existing schedule or manually initiate an import.
Import History
You can view the import history from Import History tab.
From the Import History screen you can do the following;
...