Skip to main content

Custom Execution Statuses Overview

Custom execution status brings sharper tracking to any test management workflow - learn what it is and how to set one up in TestCollab.

Updated over 3 months ago

TestCollab gives you enhanced control over how test case execution is tracked and reported. With the Custom Execution Statuses feature, you can tailor execution statuses to better match your team’s unique QA workflows.

What Are Execution Statuses?

Execution statuses are labels that indicate the outcome of a test case when it is executed. These statuses help teams track progress, identify blockers, and generate meaningful reports.

Why Add Custom Execution Statuses?

Your QA process might require states such as Needs Review, Invalid, or Environment Issue. Adding them as custom execution statuses:

  • Aligns TestCollab with your existing workflow

  • Highlights specific bottlenecks in test management reports

  • Keeps historical data intact while offering granular filters

Default Execution Statuses

TestCollab provides these five built-in execution statuses:

Status

Description

Unexecuted

Test case has not been run yet

Passed

Test case ran successfully

Failed

Test case did not pass

Skipped

Test case was intentionally skipped

Blocked

Test case couldn’t run due to a blocker

How Custom Execution Statuses Improve Test Management

  • Richer insight – Capture blockers, rework, or environment issues that default statuses miss.

  • Cleaner reports – Stakeholders see exactly where work is stuck and why.

  • Faster decisions – Priorities reflect real impact, so release calls are simpler.

Quick Start – Four Steps

  1. Open Project → Settings → Custom Statuses.

  2. Click Create Custom Status, enter a name, optional description, color, and priority.

  3. Drag to reorder statuses if you want a different display order.

  4. Start a run – the new status now appears in the picker and feeds every dashboard.

Note: The custom status feature is available for copanies on Elite or higher plans.

Did this answer your question?