Skip to main content
The requirements analysis reads your specifications, requirement documents and concepts and turns them into a structured test basis: functional modules, testable requirements and test case proposals. You review every proposal, and only what you accept is created in Test Management and in your projects. It is a part of Test Management, not a separate app. Open it from the Requirements entry of a test project, or at /{space}/test-management/requirements. Who can do this?

​
What it does

Structure

Collabase AI groups the content into functional modules and writes testable requirements for each one.

Test case proposals

For every requirement it designs positive, variant, negative and non-functional cases, with preconditions, test data, steps and expected results.

Traceable

Every requirement and case shows the source and section it comes from, and whether the source states it or it was derived.

Honest about gaps

Where a document does not define an expected result, the analysis marks an open point instead of inventing one.

​
Create an analysis

1

Choose the sources

Pick one or more Docs pages, or upload a PDF or Word document. The text of uploaded files is read and then dropped.
2

Add context

Name the roles, the focus and the level of detail you need, and the language of the result.
3

Start

Generation runs in the background. You can leave the page: the analysis shows its progress, and you get a message when it is done or has failed.
If generation fails, open the analysis and choose Retry. It continues from what was finished.

​
Review

Open the analysis to see its modules, requirements and test case proposals as lists you can filter.
  • Edit a requirement, a case or its steps. A row you edited by hand is never overwritten when you regenerate.
  • Accept or reject proposals. Rejected ones are not created.
  • Complement or regenerate one requirement, or ask for the steps of a case.
  • Review asks Collabase AI to look for gaps, such as a missing negative case. Every finding can be applied, or dismissed with a reason.
  • Coverage per requirement shows whether it is covered fully, partly or not at all.

​
Create in Test Management

Select the proposals you want and choose Transfer to Test Management:
  • Test cases are created in a test project of the space, one folder per module below a folder named after the analysis. Each case carries its steps, is linked to the work item of its requirement and shows where it came from.
  • Requirements become work items of a type and project you choose. The work item links back to the analysis.
A proposal that was already created is skipped, so you can run a transfer again for what is missing. In a project that requires approval, created cases start as drafts that a reviewer approves.

​
Settings

System administrators set how analyses are generated and transferred under Settings → AI → Requirements analysis: The analysis uses the AI provider you set up in AI configuration and no other. With a local model, your content never leaves the instance.

​
Next steps

  • Test cases explains versions and review of the cases you create.
  • Reports shows which requirements are covered by tests.
Last modified on October 24, 2026