Divengine StudioProof, not promises
A requirement says what should hold; evidence shows that it does. Studio includes a complete test management module that records what was tested, against which version, by whom and with what result, and connects it to the requirements it verifies.
Plans, suites, cases and steps
A test plan says what you will test, for which Development, in which environment and stage. Suites organize cases; cases describe objective, preconditions, data and acceptance criteria; steps pair each action with its expected result.
- Cases go from draft to ready to obsolete
- Optional steps, ad hoc scenarios promoted into the plan
- Clone plans for the next release
Runs that freeze what was tested
A run is one execution campaign by one tester. When it starts, Studio freezes a snapshot of the cases and steps, so editing the plan later never rewrites history. Testers go case by case, record each step, attach screenshots, logs or videos, and the run completes by itself.
- Evidence stored privately, never public
- Corrections of results are recorded, not overwritten
- Printable run and plan reports
A live picture of quality
The QA dashboard shows execution results across plans, stages and environments, so leads can see where verification stands without assembling a report by hand.
From a failed step to a verified requirement
Evidence is only useful when you can tell what it proves. In Studio it stays attached to the run and step that produced it, and its test cases are linked to the requirements they verify.
QA issues
Report a defect straight from the failing step, with its evidence, and follow it to closure.
Verifies
Link test cases to the requirements and use cases they verify, with explicit traces.
Readiness
Requirements without tests show up in the readiness of the Development.
Roles
QA User, Tester, Lead and Manager: everyone sees and does exactly their part.
Evidence of engineering, not only of testing
Reviews, analyses and validations produce evidence too. Studio has an Evidence record type (EVD) for evidence of engineering activity, review, verification or validation, which decisions, requirements and work products can be traced to. Baselines keep the revisions that were in force when that evidence was gathered.
Automated test results, API assertions and end-to-end evidence imported from pipelines are on the roadmap; today, results are recorded in Studio's runs.