Sync Scenarios is used to keep the scenarios created in the product aligned with the latest test automation code.

When automation code changes, the scenarios in the product may no longer match the current code structure. For example, new test methods may be added, existing methods may be removed, or scenario names may change in the repository.

With Sync Scenarios, users can compare the scenarios detected from the automation code with the scenarios currently available in the product, then import missing scenarios or remove outdated ones.

With this feature, users can:

Use Sync Scenarios when there are changes in the test automation code, such as:

This is especially useful for projects with many scenarios, where manually creating or removing scenarios one by one would take too much time.

The sync process consists of four steps:

In the Project step, select the project whose scenarios will be synchronized.

The selected project is used to detect the available test methods, specs, or scenario definitions from the automation code.

After selecting the project, continue to the next step.

The Methods to import step shows the methods/scenarios that exist in the automation code but have not yet been created in the product.

These items are treated as missing scenarios and can be created in bulk.

In this step, users can:

Example:

The Method Name represents the method or scenario detected from the automation code.

The Scenario Name represents the scenario name that will be created in the product. This name can be edited before proceeding.

Only selected methods will be created.

The Methods to remove step shows the scenarios that already exist in the product but are no longer found in the automation code.

These scenarios are considered outdated because their related method, spec, or scenario definition no longer exists in the current code.

In this step, users can:

Only selected scenarios will be removed.

If a scenario should remain in the product, it should be deselected before continuing.

The Summary step displays the result after the sync operation is completed.

This is not a confirmation step. The synchronization has already been performed when the user reaches this page.

The Summary page helps users review which changes were successfully applied.

It can include two result sections:

Each section groups results by file name and shows the operation result for each scenario.

The Created Scenarios section lists the scenarios that were created during the sync operation.

For each file, the page displays a count in this format:

Example:

This means that 1 scenario was successfully created out of 1 selected scenario.

Each scenario row includes:

A checkmark in the Status column means the scenario was created successfully.

The Deleted Scenarios section lists the scenarios that were removed during the sync operation.

For each file, the page displays the number of successfully deleted scenarios compared to the total selected scenarios.

Example:

This means that 4 scenarios were successfully deleted out of 4 selected scenarios.

Each scenario row includes:

A checkmark in the Status column means the scenario was deleted successfully.

At the end of the Summary step, users can use the available actions:

A user adds a new scenario to the automation code:

However, this scenario has not yet been created in the product.

When the user opens Sync Scenarios, the scenario appears under Methods to import. The user selects it and continues.

If there are also scenarios in the product that no longer exist in the automation code, they appear under Methods to remove. The user can select the outdated scenarios and click Sync.

After the operation is completed, the Summary step displays the result:

This means that one scenario was created successfully and four outdated scenarios were removed successfully.

It is recommended to use Sync Scenarios after meaningful automation code changes, especially when:

Using Sync Scenarios helps keep scenario definitions clean, accurate, and aligned with the latest automation code.