FlexDeploy doesn't perform any automated tests directly. This job is delegated to the great number of various testing frameworks. FlexDeploy orchestrates the testing process by performing two primary functions:
...
Click the Save button to save the changes to the testing tool and return to the list of FlexDeploy testing tools.
Issue Tracking Systems
The Issue Tracking System page, which can be accessed through the Administration menu, allows management of integrations into third-party issue tracking systems. FlexDeploy currently provides outbound integration with Atlassian Jira.
...
...
Field Name
...
Required
...
Description
...
Id
...
Yes
...
System generated identifier (read-only).
...
Name
...
Yes
...
Name of the issue tracking system (read-only).
...
Description
...
No
...
Description of the issue tracking system.
...
Ticket Number Pattern
...
No
...
Pattern of the issues within the issue tracking system, used to associate FlexDeploy builds with particular issue(s). If not specified here, the pattern will need to be defined on each project which associates to your issue tracking system. For Jira, the pattern of tickets is the key is the Jira project Key, followed by a dash (e.g. "MYPROJ-"). All tickets created for this project are prefixed by this key, making it the pattern.
...
Update Tickets on Build
...
No
...
Check this box if you want to globally update any tickets associated to FlexDeploy builds. Can be overridden at project level.
...
Build Update Comment Pattern
...
No
...
Applicable only if Update Tickets on Build is checked. The value of this property is a groovy script which evaluates to the comment you wish to update associated tickets with when a build completes successfully. Groovy variables available to the script are provided in the (x=) dropdown to the right. Can be overridden at project level.
...
Update Ticket Status on Build
...
No
...
Applicable only if Update Tickets on Build is checked. Check this box if you want to globally update the status of any tickets associated to FlexDeploy builds. Can be overridden at project level.
...
To (Build)
...
No
...
Applicable only if Update Ticket Status on Build is checked. Any associated ticket will be updated to this status whenever the build completes successfully. Can be overridden at project level.
...
Update Tickets on Deploy
...
...
Check this box if you want to globally update any tickets associated to FlexDeploy deployments. Can be overridden at project level.
...
Deploy Update Comment Pattern
...
...
Applicable only if Update Tickets on Deploy is checked. The value of this property is a groovy script which evaluates to the comment you wish to update associated tickets with when a deployment completes successfully. Groovy variables available to the script are provided in the (x=) dropdown to the right. Can be overridden at project level.
...
Update Ticket Status on Deploy
...
...
Applicable only if Update Tickets on Deploy is checked. Check this box if you want to globally update the status of any tickets associated to FlexDeploy builds when they are deployed. Can be overridden at project level.
...
To (Deploy)
...
...
Applicable only if Update Ticket Status on Deploy is checked. Any associated ticket will be updated to this status whenever the deployment completes successfully. Can be overridden at project level.
...
Resource Types
Resource types provide the ability to designate an endpoint to be of a specific type of server. Once the resource types are created and associated to an endpoint, they can be utilized on script based plugins (Shell, Windows Shell, Groovy,…) to direct workflow activity to endpoints that match the requested resource type.
Resource types can be accessed through the Administration menu. 
The resource types listed above are pre-defined resource types by the WebLogic and EBS plugins and can't be modified.