Unique Test Case IDs

In the creation of test runs, Smart will inform users if they have uploaded a test file that contains duplicate test case IDs. This is to ensure that each and every test within a test run contains a unique ID that can be referenced back to a specific scenario.

Creating a new Test Run with Unique IDs

The user will need to ensure that all Test Case IDs are unique when creating test scripts that will form part of a single test pack. There are a number of aspects that need to be taken into consideration here:

  1. Test Case IDs must be unique within each Smart template.
  2. Test Case IDs must be unique inside each Smart Test Run. The functionality will not restrict you from having duplicate Test Case IDs across multiple test runs, however for good practice this should be the case.

The image below shows an example of unique Test Case IDs within a template:

If users attempt to upload a template which contains duplicate Test Case IDs, they will see the following error message on upload:

Users will also need to ensure that the Test Case IDs are unique across multiple templates if they are being uploaded into a single test run. If we take Edit Services Dates for example, a user may have 2 templates, 1 for the USA and 1 for the UK. Inside those 2 templates there may be 2 scenarios named ESD_001 and ESD_002 in both templates.

This functionality will restrict users from uploading these templates if this is the case. The IDs should be updated to be unique. E.g. ESD_UK_001 and ESD_USA_001. See the image below for an example of proposed updates to the Test Case IDs in these templates.

Re-executing with Updated Template

When users wish to re-execute a Test Run with an updated template (see the section on re-execution with updates here: Test Run Re-execution) the same rules apply as if a new Test Run were being created:

  1. Test Case IDs must be unique within each Smart template.
  2. Test Case IDs must be unique inside each Smart Test Run. The functionality will not restrict you from having duplicate Test Case IDs across multiple test runs, however for good practice this should be the case.

If a template is uploaded that contains a duplicate Test Case ID, the following error message will show:

The error message displays 2 pieces of information, which are numbered in the image above:

  1. The duplicate Test Case ID
  2. Where the duplicate Test Case ID was found. If it is found in multiple templates it will display the name of each template containing the duplicate.