Page Comparison

Field name

Description

Job Name (required)

The name of your suite automation job.

Job Description

The description of your job.

Automation Framework

The test automation tool you are using. Possible values:

• SoapUI PRO

• TestComplete

• Cucumber

• JUnit

• Selenium

• TestNG

• Tricentis Tosca

• UFT

• Eggplant

Script Path

The check box is used to invoke a script. You can then specify the path to it in the field below.

Result Path (required)

The path to the folder that will store the results.

Create Package

Select the check box if you are using the Selenium automation framework.

ZBot (required)

The Zbot you want to use for automation.

Cycle Name (required)

The name of the cycle that will be created. Here you can decide whether you want to reuse the same test cycle for all the automation runs or create a new test cycle every time the automation job is run (you can include a timestamp in the test cycle as well).

Folder in Test Repository for Test Cases (required)

Test repository folder where the created test cases will be stored.

Select User

The Zephyr user to assign the job to.

Cycle Start Date (required)

The test cycle start date.

Cycle End Date (required)

The test cycle end date.

Reuse Scenarios

Reuse Actions and Impact

Currently using an existing test cycle and phase

A new test cycle and phase aren't created and instead reuse the same testing cycle and phase that was already created from the previous job in the Test Planning and Test Execution pages.

Currently using an existing test cycle and phase but you need to update the cycle start and end dates

A new test cycle and phase aren't created and instead will update/append the changes to the cycle's start and end dates for the test cycle and phase that already exists in the Test Planning and Test Execution pages.

Currently using an existing test cycle and phase but you need to update the person that they are assigned to

A new test cycle and phase aren't created and instead will update/append the changes to the assignee for the specific testing cycle and phase that already exists in the Test Planning and Test Execution pages.

Creating a new test phase but using an existing test cycle

When editing the phase name, the new test phase name will be created under the existing test cycle in the Test Planning, and Test Execution pages.

Using an existing test phase but creating a new test cycle

When editing the cycle name, a new test cycle name will be created under the Test Planning and Test Execution pages but there won't be a new phase created in the Test Repository.

Creating a new test phase and new test cycle

When editing both the cycle and phase name, a new test cycle name will be created in the Test Planning and Test Execution but there will not be a new test phase created in the Test Repository.