...
- 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.
- Specify a name for the test job. The job will automatically be populated with the selected test file.
- 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.
- 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.
- Enable the Batch (fastest) option to execute tests on each designated server or enable the Sequential 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.
- 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.
Click on a scenario to view the environment variables and data sources available for each scenario.
- 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
- (Optional) You can specify a context to be provisioned upon test execution by specifying the appropriate system, environment, and set of component instances.
- 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.
Verify configuration of the component instances to be provisioned and make any adjustments.
- Click Save.
...
Executing a Job without Affecting Team Members
Sometimes you You may might want to quickly run an existing job with new environment and/or variable settings—without 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 desired settings ( environment context , variables, etc.)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.
Executing Test Jobs Automatically
The Parasoft Environment Manager Plugin for Jenkins (contact your Parasoft representative for download information) can automatically run test jobs as part of a Jenkins job. This plugin is designed to help you rapidly configure various actions needed for automated, continuous testing across your software delivery pipeline. For more details, see the description and documentation available on Marketplace.
...