...
The integration with 3rd party testing tools is implemented by the use of plugins. If FlexDeploy doesn't provide a plugin for some testing tool out-of-the-box then the Shell plugin can be used instead. It allows to execute batch scripts in order to interact with the testing tool. The plugins act as adaptors for various testing tools. They command testing tools to run tests and they import test results into unified test result storage. This allows users to analyze test results using the dashboard reports, abstracting away from the exact testing tool.
Viewing Testing Tools
To view the list of testing types defined within FlexDeploy, select the Testing tab on the Integrations page and select the Providers button in the top right:
...
Creating
...
and Editing Testing Tools
To create a testing tool click the Create button on the top right of the table. To edit a testing tool, select an existing testing tool’s name in the table.
Enter values for the following fields:
Field Name | Required | Description |
|---|---|---|
Name | Yes | Name for the testing tool. |
Description | No | A description of the provider. |
Active | Yes | Whether or not the Provider is active in the system. Defaults to "Yes". (Cannot be inactivated if in use by an account) |
Properties | No | Setup one or more property key definitions for the provider which will be used for every account created for this provider. |
It is possible to define a set of properties for a custom testing tool. The values of the testing tool properties are set up on test instances created for this provider. This is useful for testing tools like OATS or Load Runner when there is a dedicated instance of the testing tool installed on a separate server.
...