Understand the Quality of Your Test Coverage
This new Inflectra.ai capability in Spira helps teams move beyond simple traceability and understand the quality of their test coverage. From the requirement details page, users can ask Inflectra.ai to evaluate how well a requirement is covered by its associated test cases. The AI analyzes the requirement’s intent, scope, acceptance criteria, and expected behavior, then compares that against the linked tests to identify where coverage is strong, incomplete, redundant, or potentially missing altogether.
The result is a structured coverage report that gives product owners, business analysts, QA leaders, and compliance teams a clearer view of testing readiness. Instead of manually reviewing every linked test case, teams can quickly see whether the requirement has meaningful validation across key scenarios, edge cases, negative paths, security considerations, or regulatory expectations. This helps reduce the risk of untested functionality, improves audit confidence, and gives teams a faster way to close quality gaps before release.
For organizations in regulated or mission-critical industries, this is especially valuable because coverage is not just about having a test case linked to a requirement; it is about proving that the requirement has been tested thoroughly and appropriately. By combining Spira’s end-to-end traceability with Inflectra.ai’s intelligent analysis, teams can accelerate review cycles, improve test design, and make better release decisions with greater confidence.
When the analysis tool finds gaps in test coverage, it suggests meaningful and actionable remediation steps:
Functionality Details
How does the requirements coverage analysis tool work exactly:
- What data is considered: The analysis considers the requirement's name, description, and steps/scenarios. For broader context, it also looks at the parent requirement hierarchy, sibling requirements, and the product name. Each linked test case is evaluated using its name, type, description, and all test steps.
- How sibling requirements are used: Sibling requirements (other children of the same parent) help define what is out of scope for the current requirement. If a testable topic is clearly a sibling's responsibility, it won't be flagged as a coverage gap. This means well-structured requirement hierarchies produce more accurate results. Up to 30 siblings are considered.
- What the output includes: The report provides an overall coverage percentage, a breakdown of testable topics with their mapped test cases, a list of uncovered topics, and actionable suggestions for improving coverage. If a linked test case appears unrelated to the requirement, it will be flagged as a potential mislink and won't count toward coverage.
In order for the analysis tool to proceed, the following minimum requirements need to be met:
- At least one test case must be linked to the requirement.
- The requirement must have either steps/scenarios or a description with at least 5 words.
- The total number of test steps across all linked test cases must not exceed 500.
- The requirement must not have more than 100 steps/scenarios.
