How Test Case Status Is Calculated

In AgileTest, a Test Case status can be updated in different ways, depending on the Test Case type and execution method:

• Manual Test Case: AgileTest calculates the Test Case status based on the individual Test Step status you map for each test step in test executions.

• Generic & Cucumber Test Cases: AgileTest updates the Test Case status by importing results from supported automation frameworks or API requests.

1. How AgileTest Calculates Manual Test Case Status From Test Steps

1.1 Test Step Status Priority Order

When a Test Case has multiple Test Steps with different statuses, AgileTest determines the overall Test Case Status using the priority order below. The first matching rule takes precedence.

Example:

1.2 Custom Test Step Status Priority

1.2.1 Create and Map a Custom Test Step Status

In addition to the default Test Step statuses, you can create custom Test Step statuses and map them to default or custom Test Case statuses.

Custom Test Step statuses follow the same Test Step Status Priority Order, based on the Test Case status they are mapped to.

1. Go to Jira Settings → Marketplace apps.

2. Select the AgileTest app and choose Test Step Statuses.

3. Click the “+ Test Step Status” button.

4. Enter the name, description, and color.

5. In Test Status, select the available status you have created in the Test Statuses settings.

1.2.2. How Custom Status Mapping Affects Test Case Status

When multiple step statuses rank the same, the most recently created Test Step status takes precedence. For the default statuses, this means a custom status wins over a default status at the same priority because custom statuses are created after the defaults.

You can see the creation order in Settings → Test Step Statuses: newer statuses are lower in the list.

Example:

2. How AgileTest Calculates Generic and Cucumber Test Case Statuses

In automation, the report file can contain many statuses for the same test case, so AgileTest can automatically calculate the overall Test Case status when you import automation results into a Test Execution.

The calculation depends on the automation framework, the imported results, and their mapped Test Statuses.

When importing automation results, AgileTest matches each result to a Test Status in the following order:

1. Find a Test Status with the exact same name as the imported result.

2. If no exact match exists, find a matching status regardless of uppercase or lowercase letters.

3. If no matching status exists, use the default status mapping below.

4. If the result is not recognized, assign TO DO .

For JUnit, TestNG, NUnit, xUnit, and Robot Framework, the default mapping is:

After importing results, AgileTest calculates the overall status from the results imported through JUnit, TestNG, NUnit, xUnit, or Robot Framework.

If a Test Case has multiple results, such as retries or parameterized test runs, AgileTest combines them using the priority order like the manual test step.

Example: