By default, a test plan in TestCollab is considered complete once every test case has been executed, regardless of whether it passed, failed, was skipped, or blocked. This works well for many teams, but sometimes you need more control.
With Test Plan Completion Statuses, you can choose exactly which execution statuses should count as "Done." For example, you can require that every test case must be Passed before the plan is marked as complete, so failed or skipped cases keep the plan "In progress" until they are resolved.
Where to find this setting
Go to your project
Click Settings in the left sidebar
Under the General tab, scroll down to Test Plan Completion Statuses
How to configure completion statuses
The setting appears as a multi-select dropdown listing all active execution statuses in your project (e.g., Passed, Failed, Skipped, Blocked, and any custom statuses you have created).
Select one or more statuses that should count as "Done"
Click Save to apply the changes
Examples:
Configuration | What it means |
(empty - default) | Any executed status counts as done. The plan completes when no unexecuted test cases remain. |
Passed | Only test cases marked as Passed count as done. Failed, Skipped, or Blocked cases keep the plan in-progress. |
Passed, Failed | Both Passed and Failed count as done. Skipped or Blocked cases need to be re-executed. |
Passed, Skipped | Passed and Skipped count as done. Failed cases must be retested before the plan can complete. |
Resetting to default behavior
If you want to go back to the default behavior (any executed status counts as done):
Clear all selected statuses from the dropdown by using "Reset to default"
Click Save
What happens when you change this setting
When you save a new configuration, TestCollab automatically recomputes the status of all existing test plans in the project. This means:
Plans that were previously marked as Done may change to In Progress if they have test cases that don't meet the new criteria
Plans that were In Progress may become Done if they already satisfy the updated criteria
This recomputation happens in the background and may take a moment for larger projects.
How this affects test plan execution
Completion during a run: When you are running test cases under a test plan with step-wise or test-case-wise execution, the "Execution finished" summary will only appear once all test cases have a status that matches your configured completion criteria; and not simply when all cases have been executed.
RUNs: If the most recent RUN of a test plan has test cases that are not in "Test Plan Completion Statuses", you will not be able to start a new RUN until the current RUN meets the completion criteria. TestCollab will show a message indicating that the previous RUN is still unfinished.
Test plan status on list and grid views The status shown on the test plans list (Not Started, In Progress, Done) reflects the configured completion criteria. If you have set completion statuses, a plan will only show as Done when every test case has one of the selected statuses.
Points worth noting
The Unexecuted status cannot be selected as a completion status, test cases must be executed at least once
If a status is deactivated in your project after being included in this setting, it will be automatically removed from the completion criteria
Custom statuses are fully supported, if you have created custom execution statuses, they will appear in the dropdown alongside the default ones
This setting is project-specific, each project can have its own completion criteria
Only project administrators can configure this setting