✅ Best Practices
Use unique, clear and self-descriptive names for custom statuses.
Assign colors that are intuitive and easy to differentiate at a glance.
Review priorities regularly to align with team processes.
📅 Common Use Cases
Pending Design: Waiting on design input before testing
Needs Retest: Issue resolved, ready for a fresh test
Needs Review: Needs QA approval or peer verification
Invalid: Test is no longer relevant or applicable
❓FAQs
What are custom statuses, and why do I need them?
Custom statuses allow you to define test execution results beyond the default ones provided by TestCollab. This gives your team the flexibility to better reflect real-world scenarios during test execution and reporting.
Can I choose not to use custom statuses?
Yes! Custom statuses are completely optional. If the default statuses suit your project needs, you can continue using them as is.
Will I lose my test execution data if I start using custom statuses?
Not at all. All your previously recorded execution results remain intact. You can continue accessing them through execution status history, logs and reports as you did earlier.
What changes can I expect while using custom statuses?
You’ll be able to customize your list of execution statuses per project. This means you might have fewer or more status options available during the test case execution, and those choices will be reflected across reports and dashboards.
I use API, how do I make use of custom statuses?
Teams using the REST API have two options for referring to default statuses:
You can either use the existing numeric identifiers (0 for unexecuted, 1 for passed, 2 for failed, 3 for skipped, 4 for blocked), or you can directly use their system names ("unexecuted", "passed", etc.) for better readability.
For newly added custom statuses, use the System Name shown on the Custom Statuses page. This ensures consistency and compatibility when executing test cases via API.
Can I have a different set of statuses for each project?
Yes. Custom statuses are project-specific. You can configure different sets of statuses for different projects based on your team's workflow.
How can I configure custom statuses for my project?
It’s simple! An administrator or a project member with a role that allows operations in custom statuses, can go to the "Custom Statuses" option under the "Settings" menu within a project and create, edit, or deactivate statuses as needed.
How does the app decide which status takes precedence?
The priority value assigned to each status determines its precedence. When a test case includes steps with different statuses, the one with the highest priority will be used as the overall result for that test case.