Duette Schedules allows you to create schedules where individual or multiple sets of result files can be imported into Enterprise Tester, with the associated automated test, automated test assignment and runs being created automatically.
Features
Duette Schedules supports the following features:
- Ability to schedule importing on an ad-hoc, periodic or daily basis.
- Support for multiple schedules.
- Support for record summary and details history of imports.
- Ability to manually trigger an import schedule.
- Ability to import multiple files using a file name "capture" within the source path of the tests.
- Ability to import multiple files using a folder name "capture" within the source path of the tests (can not be combined with filename capture).
- Ability to combine multiple source files into a single automated test result.
- Ability to either always import results on scheduled run, or only import results if the source files have changed since last time.
- Ability to duplicate an existing import configuration.
- Ability to enable or disable import configurations and schedules.
- Ability to automatically maintain only a certain number of result files (automatically purging the oldest runs over the maximum number of retained results).
Creating an Import Schedule
You can configure Duette Schedules from the Resources tab of the tree view navigator. When the Duette Plugin is enabled, a section called "Duette Schedules" is available.
...
Using the Source Path and Name Template
Example - 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 with an assign the a name.
Source Path: c:\testdata\results.xml
Name Template: my results
Example - Creating an Automated Test from a Folder a of Results
Source Path: c:\testdata\
Name Template: my results
These both behave in the same manor as manually import an automated test result and filling in the "Results Path" field on screen. In addition, 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).
Examples - 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, here is an example using files:
Source Path: c:\testdata\{name}.xml
Name Template: {name}
For a directory of files, here's what would be generated:
...
| File | Generated Name | Comments |
|---|---|---|
| c:\testdata\build123\ | build123 | |
| c:\testdata\builder456\ | build456 | |
| c:\testdata\test.xml | skipped, file not a folder |
Limitations
There some limitation so the Source Path and Name Template fields. These include the following:
- A folder name with a file cannot be captured e.g. "c:\testdata\{name}\input.xml" is not supported.
The combine results option is not supported for zip files e.g. "c:\testdata\{name}.zip".
The combine results option is not supported when capturing folders e.g. "c:\testdata\{name}\" you can not used the "combine results" option.
If capturing files which include zip and non-zip files, the zip files will not be automatically expanded/traversed (but you can use the "combine results" option). In this case zip files are treated like any other file making up a single result.
Configuring the Schedule
Now that your configuration is complete you are ready to set up your import schedule. The import frequency can be configured from the Schedules tab. There are 3 options that can be configured:
...
You can use the tool bar to add a 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 both the configuration screen.. From the configuration screen you can view all synchronization events, select to only view errors, export the synchronization events to a csv file or clear the history.
...