Test Management keeps what you test and what came out of it. Manual testers work through cases in Collabase. Your CI pipeline sends its results in, and both end up in the same cycle.Keys are stable.
How it is organized
Test cases
A case has steps, a priority and a type. Every change is a new version, and only an approved version can be run.
Cycles
A cycle plans a set of cases for a release or a sprint, assigns them and collects the results.
CI imports
Send JUnit XML or Playwright JSON from your pipeline. Tests that match no case wait for your decision.
Requirements analysis
Collabase AI turns specifications into requirements and test case proposals you review and create here.
Reports
Coverage of requirements and work items, the release gate and the results over time.
Settings
Review rules, roles, the key prefix and how a project is archived.
Structure
QA-T12 is the twelfth case of the project with the prefix QA, and it stays QA-T12 when you move or rename it. Addresses use the key too, for example /my-space/test-management/QA/cases/QA-T12.A typical flow
1
Write a case
Create it in a folder with steps and expected results. It starts as a draft.
2
Get it approved
Submit the version for review. A reviewer approves it, or sends it back with a reason.
3
Plan a cycle
Pick cases, folders or all approved cases, and assign them to testers.
4
Run and import
Testers record results step by step. CI results arrive through the import.
5
Check coverage
Open the reports to see which requirements have no passing test, and close the cycle when the release is done.
Who can do what
A project is open to everyone in the space until you name people or groups in its roles. From then on only those people and space administrators can open it.