Sign inCreate free account

Industries

Requirements and test evidence for software teams, beside the issue tracker

A software team can keep what the product must do in OpenV, link each requirement to the automated tests that prove it, and record every test run from its pipeline through the API. It sits beside the issue tracker and does not replace it: tickets say what to do next, requirements say what must stay true. OpenV has no built-in sync with an issue tracker, so the link between a ticket and a requirement is a reference you write.

Updated by Desktop Machine Shop, the makers of OpenV.

What these teams keep

A ticket is closed when the work is done, and what the product must do is then spread across hundreds of closed tickets. Teams that answer to customers or auditors, for SOC 2, ISO 27001 or a contract, need the current set of requirements in one place, each with the test that shows it holds. ISO/IEC/IEEE 29148 describes what a good requirement looks like.

Where it goes in OpenV

  • Requirements are written once and versioned. Their wording is checked against ISO/IEC/IEEE 29148 “shall” rules or RFC 2119, as advice.
  • A test case names the automated test that verifies a requirement. A pipeline step records a test run with a result for each.
  • Target releases say which requirements are in which version, and a release shows how many are verified.
  • An AI coding client connects over MCP, reads the requirements it is working to and proposes changes for a person to approve.
  • OpenV’s own requirements, design and tests are kept this way, in an OpenV project.

A first project

Write the ten requirements a customer would hold you to. Add a test case for each that names an existing automated test, and record one run from your pipeline. The coverage figure is then a fact about your product that you can show.

What OpenV does not do

  • No certification, no tool qualification kit and no claim of compliance with any standard named on this page. OpenV holds the record; your process and your assessor decide whether it is enough.
  • No built-in sync with Jira, GitHub Issues or any other tracker.
  • No link from a requirement to lines of code or to code coverage.
  • Embedded software in a regulated product is covered by that product’s sector page, not this one.
  • No electronic signatures, and no separate approver role: any project editor can approve, including their own change.
  • OpenV is in alpha: screens still change between releases, though data, exports and the API stay compatible across stable releases.

Read more