Test Case Progress & Custom Step Statuses

AXQA tracks execution at Step level and calculates Test Case Progress from the current Step Statuses.
In addition to the standard system statuses, projects can define custom status names and colors while preserving consistent reporting logic.

Why it matters

• Shows how much of a Test Case has actually been executed.
• Allows teams to use terminology that matches their QA process.
• Keeps custom workflows compatible with AXQA reporting and calculations.

When to use it

• When tracking Manual Test Case execution.
• When reviewing Test Case completion.
• When your QA process requires status names beyond the standard AXQA labels.
• When analyzing partially executed Test Cases.

Core concepts

• System Status Type – The underlying AXQA status used for calculations.
• Custom Status – A project-specific display status with a custom name and color.
• Progress – The percentage of Test Steps that have been executed.
• Case Status – The calculated overall state of the Test Case.
• Mark All Passed – An action that marks every Test Step as Passed.

How it works

1. Every Test Step has a status.
2. AXQA maps the displayed status to a system status type.
3. Executed and Not Run steps are counted.
4. AXQA calculates Test Case Progress.
5. The overall Test Case Status is calculated from the Step Statuses.
6. Status information is captured in execution history.

How to use it

Step 1: Understand the system status types

AXQA uses five system status types:

• Not Run
• Passed
• Failed
• Error
• Skipped

These system types drive calculations and reporting.

Step 2: Create custom statuses

Authorized users can create project-specific Step Statuses.

A custom status includes:

• Name
• Color
• System Status Type

AXQA displays Blocked to the user while treating it as the mapped system type for calculation purposes.

Step 3: Update Step Status

Select the appropriate status for each Test Step.

Changing a Step Status updates the Test Case Progress and overall state.

Step 4: Understand Progress

Progress measures execution completion.

The following statuses count as executed:

• Passed
• Failed
• Error
• Skipped

The following remains incomplete:

• Not Run

Eight steps have been executed.

Test Case Progress:

This does not mean the Test Case has an 80% pass rate.

Step 5: Use Mark All Passed

The Test Case Manager provides a Mark All Passed action.

When used:

• All Test Steps are changed to Passed.
• Test Case Progress becomes 100%.
• An execution-history record is created.
• The status changes are included in the Test Case audit trail.

Step 6: Manage custom statuses

Custom statuses can be removed when they are no longer required.

However:

• AXQA system statuses cannot be deleted.
• System statuses cannot be overwritten.
• A custom status cannot be deleted while existing Test Steps are using it.

Best practices

• Use custom names only when they provide meaningful workflow value.
• Map custom statuses to the correct underlying system type.
• Do not use Progress as a quality or pass-rate metric.
• Keep status terminology consistent across the project.
• Review status mappings before using them in reporting.

Common mistakes

❌ Interpreting 100% Progress as 100% Passed.
✔ Progress means every step has been executed, even if some steps Failed or were Skipped.

❌ Creating a custom status without considering its system mapping.
✔ Select the system type that reflects how AXQA should calculate and report the status.

❌ Trying to delete a custom status currently used by Test Steps.
✔ Update the affected steps first, then remove the unused status.

Security & permissions

• Custom Step Statuses are scoped to the Current Project.
• Creating or deleting custom Step Statuses is restricted to Staff or Superuser accounts.
• AXQA system statuses cannot be deleted or overwritten.
• Status changes are included in supported audit and execution-history workflows.
• Historical execution records preserve status information for reporting.

Related documentation

• Test Steps Fundamentals
• Running a Test Case
• Test Case Manager Overview
• Test Case Audit History
• Execution History