Use case · Software V&V lead
Know which requirements were tested on this version
Before a release, someone always asks: which requirements were actually tested, and did those tests pass on this version? For medical device software, IEC 62304 expects traceability between software requirements and their verification, and ISO 13485 expects verification records you can show.
The job
Your requirements live in Jira. You plan the verification of each version, run the tests, raise the defects, and hand over a record that ties every requirement to its tests and their results.
Before
- Test cases live in a spreadsheet, next to Jira but not in it.
- A failed test becomes a bug typed by hand, without the steps that led to it.
- The traceability matrix is rebuilt for each release, and is out of date by the evening.
- Nobody can say which version of a test case was run, or who signed the results.
After, with Clearlane Tests
- Test cases sit next to the Jira requirements they cover: stories, epics or any type you choose. Nothing to configure in Jira first.
- A campaign per version or sprint: pick the cases, assign them, follow who runs what.
- Run step by step; a failed step becomes a Jira bug in one click, steps to reproduce included, linked to the requirements the test covers.
- Each requirement shows its coverage: not covered, not run, failed or passed. It also works in JQL, filters and dashboards.
- Close the campaign: it is sealed, signed if your project asks for it, and exported as a PDF report.
What sets it apart
- The exact version that was run. Each run keeps a snapshot of the test case version that was executed.
- Your level of proof. No signature, one at the end of a campaign, or one for every run, chosen per project.
- Sealed at closure. A fingerprint of the campaign, checked again on screen, and a PDF report with coverage, results, signatures and history.
- Runs on Atlassian. Your data stays in your Atlassian site.
What it does not do
It does not write your test plan or decide what counts as enough testing. It helps you keep verification records; it makes no claim of certification, and validating it for your own intended use remains your responsibility.