Requirements Coverage Gaps
How to review AI-identified coverage gaps in your uploaded requirements, inspect gap details with similarity scores, and accept or dismiss AI-suggested test cases.
Who is this for? QA engineers, testers, and QA managers who upload requirement documents and want to identify which requirements lack adequate test coverage.
When you upload a requirements document, ContextQA's AI engine analyzes it against your existing test cases and identifies coverage gaps — requirements that are not yet tested or only partially covered. The Gaps tab shows these gaps with similarity scores, and you can accept AI-suggested test cases to close them.
Prerequisites
A ContextQA workspace with AI features enabled.
At least one requirement document uploaded through the Import Requirement option (see Creating Test Cases).
The uploaded file must have finished processing (status: Completed or Pending Action).
Opening the requirements library
In the left navigation, go to Test Development.
Select Imported Files.
The Imported Files list displays all uploaded requirement documents with their status, test case count, and creation details.
Click a file name to open the file details view.
Filtering by test plan: Use the test plan filter dropdown above the list to narrow results. Type to search across your test plans — the filter supports server-side search with pagination.
Understanding file statuses
Completed
Processing finished. Test cases and gap analysis are available.
Pending Action
The AI needs clarification before generating test cases. Answer the questions or skip to generate immediately.
Processing
The file is still being analyzed. Refresh the page to check progress.
Failed
An error occurred during processing. Check the error details and re-upload if needed.
Answering AI clarification questions
When a file has Pending Action status, ContextQA's AI has questions about your requirements to improve test generation accuracy.
Click the file name. The Help AI Understand Your Requirements dialog opens.
Review each question. The AI provides context explaining why it needs this information.
Enter your answers in the text fields.
Click Submit to send your answers and start test generation.
To skip the questions, click Skip & Generate Test Cases. The AI generates test cases using its best interpretation of the requirements.
Answering questions improves accuracy. Providing answers helps the AI generate more relevant test cases and more accurate gap analysis. Skip only if the requirements are straightforward.
Reviewing the gaps tab
Once a file finishes processing, the file details view shows multiple tabs. Select the Gaps tab to see AI-identified coverage gaps.
Each gap card displays:
Requirement identifier — the requirement ID (e.g., REQ-001) and type tag.
Priority — the assessed priority level of the gap.
Similarity score — a percentage indicating how closely the requirement matches existing test cases. A lower score means less coverage.
Summary — a brief description of what the gap covers and why it was flagged.
Missing prerequisites — any prerequisites identified as missing from current test coverage.
What the similarity score means
80–100%
Well covered
Review for edge cases only
50–79%
Partially covered
Review suggested test cases
0–49%
Poorly covered
Strongly consider adding suggested test cases
No gaps found? If the Gaps tab shows "No gaps found — All requirements are well covered," your existing test cases already provide adequate coverage for this requirements document.
Inspecting gap details
On a gap card, click View details.
The gap detail drawer slides open from the right side of the screen.
The drawer displays:
Similarity score ring — a visual indicator showing the coverage percentage with color coding (green for high, amber for medium, red for low).
Summary — a detailed explanation of the coverage gap.
What's missing — a list of specific items not covered by existing test cases.
AI-suggested test cases — test cases the AI recommends creating to close the gap. Each suggestion includes a confidence badge indicating how well it addresses the gap.
Press Esc or click outside the drawer to close it.
Accepting AI-suggested test cases
Accept a single suggestion
Open the gap detail drawer for a gap.
Review the suggested test case details (title, steps, expected results).
Click Add to Test Cases on the suggestion you want to accept.
The test case is created and added to your test suite.
Accept all suggestions for a gap
In the gap detail drawer, click Add All to accept every pending suggestion at once.
All suggested test cases are created and added to your test suite.
Accept all suggestions from the gaps tab
On the Gaps tab, click Add All Test Cases to bulk-accept all AI suggestions across every gap.
All pending suggestions for the entire requirements document are created as test cases.
Review before bulk accepting. While the AI generates relevant suggestions, review the gap details and similarity scores before accepting all suggestions. Some may need manual refinement after creation.
Dismissing a gap
If a gap is not relevant, click Dismiss in the gap detail drawer. The gap is removed from the active list.
Viewing generated test cases
After accepting suggestions or once processing is complete, view the generated test cases:
In the file details view, select the Test Cases tab.
Test cases are grouped into two sections:
Newly Created Test Cases — labeled "New," these are test cases generated from your requirements.
Existing Test Cases — labeled "Duplicate," these match tests already in your repository.
Click a test case ID to open it in the test steps editor.
Tips and best practices
Upload focused requirements documents. Smaller, well-scoped documents produce more accurate gap analysis than large, broad documents.
Answer clarification questions. Providing context improves both test generation and gap detection accuracy.
Review low-similarity gaps first. Gaps with scores below 50% represent the largest coverage risks and should be addressed first.
Refine accepted test cases. AI-generated test cases are a starting point. After accepting, review and adjust steps, test data, and assertions as needed.
Re-upload after major changes. If your requirements change significantly, upload the updated document to get fresh gap analysis.
Related pages
70% less human effort with AI test generation and self-healing. Book a Demo → — See AI generate, execute, and maintain tests for your application.
Last updated
Was this helpful?