Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

The “Automated results filter” can be useful where you have one Test Automation job which runs tests for multiple Jira projects, and you only want results for test scenarios to be imported for each project.

The toggle can be found on the AssertThat Config pages which can be found in Project Settings. If you don’t have access to this page please contact your Jira Admin. The below screenshot shows the Config page for Server/Data Center:

By default (with the toggle set to off) when the test automation results are imported, and a scenario doesn’t exist in a project, the test results will be imported and a label will be added next to the stating “SCENARIO MISSING” .

With the toggle enabled, scenarios will only be loaded to a project where the AssertThat scenario exists in the project.

Trouble shooting:

Toggle enabled and my scenario exists in AssertThat however the results haven’t been loaded for one of my scenarios?

Make sure that the scenario title and feature title match exactly between what is in the Cucumber.json file and the scenario loaded in to AssertThat.

Make sure that scenario mode is set to ‘automated’.

Toggle disabled and “SCENARIO MISSING” label added but my scenarios exists in AssertThat?

Make sure that the scenario title and feature title match exactly between what is in the Cucumber.json file and the scenario loaded in to AssertThat.

I’m on Server / DataCenter and I can’t see the toggle?

For Server, check with your Jira Admin that you are on AssertThat version 1.11.5 or later.

For DataCenter, check with your Jira Admin that you are on AssertThat version 1.11.5 or later.

  • No labels