Our documentation site has been updated to AIO Tests Knowledge Base

Run Statuses

Owned by Noopur Varshney [AIO Tests]
Last updated: Dec 06, 2023
5 min read

Users can customize the run status to suit their organization's process. This article covers rules governing the run statuses and ways to customize them.

Overview

Run Statuses can be found under Project Settings as shown below.

Only Jira/Project admins or designated AIO Admins can take actions on this page. For other users, the page will be shown in a read-only manner.

On AIO Tests, each run status has a Highlight color, Type and Execution Completed flag associated with it. 

The test management tool allows users to assign colors for highlighting the statuses they have defined. Admin can choose any color of their preference for each of the Run Statuses to differentiate between different types of run statuses. 

To change the color of a run status, users need to click on the Plus (+) icon for the desired run status in the Highlight color column and choose the color of their preference by using any of the three methods. Once you have selected the desired color, click on the Save button to apply the changes. The black background shows how the color will look if ‘Dark Theme’ is being used.

Note: Users can also enter the HEX code/RGB value to select the color of their preference for Run/ Execution statuses. 

Once the admin sets the color for the Run/Execution statuses, each user can choose how they want to use the execution status highlight by selecting the desired theme customization option in My Settings.

 

Run status type determines the meaning and behavior of the run status. Run status types are NOT RUN, IN PROGRESS, PASSED, FAILED & BLOCKED.

Execution completed flag is used in reports to determine the execution of which Case is considered as done in a Cycle. This has direct impact on reports showing incomplete and done work.

 

By default, AIO Tests comes with 5 run statuses - Not Run, In Progress, Passed, Failed and Blocked.

Below operations can be performed for run statuses:

  • New run status can be created and mapped to one of the types.

  • Existing run status can be renamed and re-ordered.

  • An existing run status can be deleted.

Each project will have its own set of Run Statuses. You can use “Import Settings“ under Project Settings to copy the settings from an existing project where customization is already done.

Adding a new Run Status

To add a new run status, click on Add as shown below.

Provide the name, select type and ‘Execution Completed’ flag and click on Save.

Note:

  1. A new status cannot have a name that already exists.

  2. Once a run status is created, it’s type cannot be changed.

  3. Execution completed flag can be updated only for run statuses of type FAILED.

  4. First run status of type NOT RUN will be used as the default status for any new Run created in the Cycles.

Editing Run Status

Users can edit the existing run statuses by clicking on the pencil icon as shown below and perform necessary actions. Click on Save to confirm changes.

Reordering Run Statuses

The order in which the run statuses appear here is the order in which they show in the Status drop-downs in the rest of the app.

Users can change the order by clicking on Reorder as shown below. The handle appears next to each status, so that users can drag and drop for the desired order. Click Done to save the new order.

Deleting Run Status

Users can delete an existing run status. While deleting a run status, users need to specify an alternative run status. All the existing runs in the deleted run status will be moved to the alternative run status.

To delete a run status click on the delete icon next to the status.

 

Deletion of a run status is done via a batch job that runs every 5 minutes. While the status is marked for deletion, users cannot delete the specified alternative status.