Test Name:Gap Analysis renders and JSON is complete for QA Manager
Feature:Gap Analysis UI
User Role:QA Manager
Traceability:@SHIFT-24
Description:Verifies that a QA Manager can run a Gap Analysis on a BDD test file and receive complete, well-structured output covering both coverage and robustness gaps.
This Test Verifies:
Verification Step
What It Checks
Documentation and analysis appears in output panel
The Gap Analysis add-on produces visible results after submission
Coverage Gaps appears exactly once
The output contains a single, non-duplicated Coverage Gaps section
Robustness Gaps appears exactly once
The output contains a single, non-duplicated Robustness Gaps section
JSON output has no unresolved values
All placeholders or template tokens in the downloaded JSON are fully populated
JSON has top-level key gap_analysis
The downloaded JSON follows the expected schema structure
gap_analysis section has a non-empty coverage_gaps
At least one coverage gap was identified and recorded in the output
coverage_gaps appears exactly once in gap_analysis
The JSON structure is clean with no duplicated keys
Test Name:Gap Analysis renders and JSON is complete for Product Owner
Feature:Gap Analysis UI
User Role:Product Owner
Traceability:@SHIFT-24
Description:Verifies that a Product Owner can run a Gap Analysis on a BDD test file and receive complete, well-structured output covering both coverage and robustness gaps.
This Test Verifies:
Verification Step
What It Checks
Documentation and analysis appears in output panel
The Gap Analysis add-on produces visible results after submission
Coverage Gaps appears exactly once
The output contains a single, non-duplicated Coverage Gaps section
Robustness Gaps appears exactly once
The output contains a single, non-duplicated Robustness Gaps section
JSON output has no unresolved values
All placeholders or template tokens in the downloaded JSON are fully populated
JSON has top-level key gap_analysis
The downloaded JSON follows the expected schema structure
gap_analysis section has a non-empty coverage_gaps
At least one coverage gap was identified and recorded in the output
coverage_gaps appears exactly once in gap_analysis
The JSON structure is clean with no duplicated keys
Test Name:Gap analysis with regression layer passes layer context through to metadata
Feature:Gap Analysis UI
User Role:QA Manager
Traceability:@SHIFT-10
Description:Verifies that selecting the Regression / Smoke testing layer correctly records that context in the output metadata when running a Gap Analysis.
This Test Verifies:
Verification Step
What It Checks
Documentation and analysis appears in output panel
The Gap Analysis add-on produces visible results after submission with a testing layer selected
JSON output has no unresolved values
All placeholders or template tokens in the downloaded JSON are fully populated
JSON shiftdoc metadata includes testing layer regression
The chosen testing layer is correctly passed through and stored in the output metadata
Test Name:Gap analysis with unit layer passes layer context through to metadata
Feature:Gap Analysis UI
User Role:QA Manager
Traceability:@SHIFT-10
Description:Verifies that selecting the Unit testing layer correctly records that context in the output metadata when running a Gap Analysis.
This Test Verifies:
Verification Step
What It Checks
Documentation and analysis appears in output panel
The Gap Analysis add-on produces visible results after submission with a testing layer selected
JSON output has no unresolved values
All placeholders or template tokens in the downloaded JSON are fully populated
JSON shiftdoc metadata includes testing layer unit
The chosen testing layer is correctly passed through and stored in the output metadata
Test Name:Gap Analysis renders and JSON is complete for <role>
Feature:Gap Analysis UI
Type:Scenario Outline
Traceability:@SHIFT-24
Journey:A user selects the Gap Analysis add-on for a given role, uploads a BDD fixture, triggers analysis, and verifies that the output panel and downloaded JSON both contain complete, well-formed gap analysis data with no unresolved values.
Examples
Role
QA Manager
Product Owner
Test Name:Gap analysis with regression layer passes layer context through to metadata
Feature:Gap Analysis UI
Traceability:@SHIFT-10
Journey:A QA Manager selects the Gap Analysis add-on with the 'Regression / Smoke' testing layer, uploads a BDD fixture, triggers analysis, and verifies that the downloaded JSON metadata correctly reflects the 'regression' testing layer.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Gap analysis with regression layer passes layer context through to metadata
User is on the Analyze page
Selects format 'bdd', role 'QA Manager', add-on 'Gap Analysis', testing layer 'Regression / Smoke', uploads 'bdd_sample.feature', and clicks 'Document and analyze test cases'
Output panel shows documentation and analysis; downloaded JSON has no unresolved values and shiftdoc metadata includes testing layer 'regression'
Positive
Test Name:Gap analysis with unit layer passes layer context through to metadata
Feature:Gap Analysis UI
Traceability:@SHIFT-10
Journey:A QA Manager selects the Gap Analysis add-on with the 'Unit' testing layer, uploads a BDD fixture, triggers analysis, and verifies that the downloaded JSON metadata correctly reflects the 'unit' testing layer.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Gap analysis with unit layer passes layer context through to metadata
User is on the Analyze page
Selects format 'bdd', role 'QA Manager', add-on 'Gap Analysis', testing layer 'Unit', uploads 'bdd_sample.feature', and clicks 'Document and analyze test cases'
Output panel shows documentation and analysis; downloaded JSON has no unresolved values and shiftdoc metadata includes testing layer 'unit'