Test Scenario Versioning (From the IntelliJ)

Test Scenario Versioning (From the IntelliJ)

With this feature, we can add different versions to our tests, so we can test the different versions of an application in a more structured way.

In order to use scenario versioning the user has to export a test plan: 5 - Export to Jira / XRay (IntelliJ)

  • The fix version is mandatory and has to be valid. The user can check the available versions in Jira.

On server, select an existing ticket from the project, where the export should be done, then select the ‘Click to edit’ button (The fix version options could be different in every project, this is just an example).

On cloud, select an existing ticket from the project, where the export should be done, open the more fields and click in the fix versions field (The fix version options could be different in every project, this is just an example).

  • In the IDE (IntelliJ) add the fix version into the according input field.
    Because the fix version is mandatory the user can see the red warning icon if the input field is empty.

image-20250114-110536.png

 

If the test plan has been already exported before and has a valid fix version, the next export will update the existing test plan with the related scenarios.

If the user wants to use the scenarios in the test plan for a new version, he/she has to click the ‘Create new Testplan’ checkbox and enter the value of the new version. The export creates the new test plan with the new version and the scenarios get the version of the new test plan.

image-20250114-110722.png

 

A test plan can only have one version.

If the scenarios already had a fixed version, they will also bring it with them. (A scenario carries the version of each test plan in which it is present)

In this example, the test plan was exported with the 'henning' version, and the scenario in the test plan is already included in another test plan whose version is 'xyz' (Server).

 

Related content