...

You can filter the available jobs to focus on specific systems and environments of interest.

Image Removed

Image Removed

Adding Test Jobs

1. You can either click the add new job button (+) in the jobs list or click Create Job in the scenario details view to begin adding a job. 
    
2. Specify a name for the test job. The job will automatically be populated with the selected test file.
3. Specify a test configuration to run when the job executes. If no test configuration is specified, then the default configuration on the server will be used.  
4. CTP automatically saves a history of job executions. If you want to limit the saved history, specify the maximum days and/or runs you want to allow. 
5. Enable the Batch (fastest) option to execute tests on each designated server or enable the Sequential option  option to control the execution order. The Batch (fastest) option optimizes performance, but the Sequential option enables you to drag and drop tests into a specific order. The Sequential option also generates a separate report for each test scenario. 
   Image Removed Image Added
6. Click Add Test Scenarios and click Add to specify which test scenarios you want to run in the job. By default, each scenario will be added with the variables from the active variable set (also known as a SOAtest environment). You can hover over the test name and choose which variable set to add with each scenario. The green ball icon marks the environment that is currently active for the test scenario on the SOAtest server.
   

7. Click on a scenario to view the environment variables and data sources available for each scenario.
    

8. If multiple environments are available for the scenario, you can choose which environment to enable from the Variable Set drop-down menu. Variable sets defined in the test scenario will automatically be configured to use the existing values, but you can choose Literal from the drop-down menu and specify specific values. Literal fields are pre-populated with local variables if available. See Configuring Variable Mappings for additional information
    
9. If the .tst contains references to data sources, the job will run the rows of data specified in each data source from the .tst by default. You can enter all to configure the job to run all rows.
   
   You can choose a data source from the drop-menu and specify which rows to run.
    
10. (Optional) You can specify a context to be provisioned upon test execution by specifying the appropriate system, environment, and set of component instances.
    Image RemovedImage Added
    1. Choose a system, environment, and an instance from the drop-down menus. You can also choose Custom from the Select an Instance drop-down menu to manually configure the active component instance settings.

    2. Verify configuration of the component instances to be provisioned and make any adjustments.
        

11. (Optional) The XSL file must be the absolute filepath for the xsl file that exists on the soavirt war deployment server. (CTP and the war file can be on different servers.)
    Image Removed
    

    Once configured correctly, the user can view the report from the Job History by clicking View report.
    Image Removed

12.  (Optional) You can enable sending results to DTP by selecting the Publish checkbox and specifying the following:
    - DTP project (if not specified, the results sent to DTP will be associated with the Default Project)
    - Build ID 
    - Session tag
    Connection to DTP must be properly configured for the results to be sent to DTP; see Connecting to DTP.
    This functionality requires SOAtest 2021.2 or later.
    Image Removed
13. Click  Click Save.

Executing Jobs

Jobs can be executed directly from the UI, or as part of an automated Jenkins job.

...

Executing a Job without Affecting Team Members

You may might want to quickly run an existing job with new environment and/or variable settings without saving changes to that job and potentially impacting other team members who are also working with that job. In this case, just select the job, configure the environment context and/or variables, and click Executewithout first saving the job. Be sure to select the top-level job node rather than a time-stamped job history node. Other changes, such as renaming the job, setting a different history limit, test configuration, requires saving the updates. Users with the provision role can make adjustments in order to customize their job executions, but cannot save changes.

...