Test Name:All add-ons - sections present in JSON output for QA Manager
Feature:Add-ons Analysis
User Role:QA Manager
Traceability:@SHIFT-15
Description:Verifies that when a QA Manager analyzes a BDD test file with all add-ons enabled, the downloaded JSON output contains fully populated sections for technical review, gap analysis, annotation summary, risk assessment, and recommendations.
This Test Verifies:
Verification Step
What It Checks
Documentation and analysis appears in output panel
The analysis runs successfully and results are visible to the user
JSON output has no unresolved values
All fields in the output are populated — no placeholders or missing data remain
JSON has top-level key 'technical_review' with non-empty 'test_quality'
The technical review add-on produces quality assessments for the uploaded tests
JSON has top-level key 'gap_analysis' with non-empty 'coverage_gaps'
The gap analysis add-on identifies areas of missing test coverage
JSON has top-level key 'annotation_summary' with non-empty 'annotation_health'
The annotation summary add-on evaluates the health and completeness of test annotations
JSON has top-level key 'risk_assessment' with non-empty 'scenario_risk_ratings'
The risk assessment add-on assigns risk ratings to individual test scenarios
JSON has top-level key 'recommendations' with non-empty 'actions'
The recommendations add-on produces actionable next steps based on the analysis
Test Name:All add-ons - sections present in JSON output for Product Owner
Feature:Add-ons Analysis
User Role:Product Owner
Traceability:@SHIFT-15
Description:Verifies that when a Product Owner analyzes a BDD test file with all add-ons enabled, the downloaded JSON output contains fully populated sections for technical review, gap analysis, annotation summary, risk assessment, and recommendations.
This Test Verifies:
Verification Step
What It Checks
Documentation and analysis appears in output panel
The analysis runs successfully and results are visible to the user
JSON output has no unresolved values
All fields in the output are populated — no placeholders or missing data remain
JSON has top-level key 'technical_review' with non-empty 'test_quality'
The technical review add-on produces quality assessments for the uploaded tests
JSON has top-level key 'gap_analysis' with non-empty 'coverage_gaps'
The gap analysis add-on identifies areas of missing test coverage
JSON has top-level key 'annotation_summary' with non-empty 'annotation_health'
The annotation summary add-on evaluates the health and completeness of test annotations
JSON has top-level key 'risk_assessment' with non-empty 'scenario_risk_ratings'
The risk assessment add-on assigns risk ratings to individual test scenarios
JSON has top-level key 'recommendations' with non-empty 'actions'
The recommendations add-on produces actionable next steps based on the analysis
Test Name:All add-ons - sections present in JSON output for QA Manager
Feature:Add-ons Analysis
Traceability:@SHIFT-15
Journey:A QA Manager selects all add-ons, uploads a BDD fixture, triggers analysis, and verifies that the downloaded JSON output contains all five expected top-level add-on sections with non-empty content.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
All add-ons - sections present in JSON output for QA Manager
User is on the Analyze page with format 'bdd', role 'QA Manager', and all add-ons selected
User uploads 'bdd_sample.feature' and clicks 'Document and analyze test cases', then downloads the JSON output
JSON output contains no unresolved values and has non-empty top-level keys: technical_review (test_quality), gap_analysis (coverage_gaps), annotation_summary (annotation_health), risk_assessment (scenario_risk_ratings), recommendations (actions)
Positive
Test Name:All add-ons - sections present in JSON output for Product Owner
Feature:Add-ons Analysis
Traceability:@SHIFT-15
Journey:A Product Owner selects all add-ons, uploads a BDD fixture, triggers analysis, and verifies that the downloaded JSON output contains all five expected top-level add-on sections with non-empty content.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
All add-ons - sections present in JSON output for Product Owner
User is on the Analyze page with format 'bdd', role 'Product Owner', and all add-ons selected
User uploads 'bdd_sample.feature' and clicks 'Document and analyze test cases', then downloads the JSON output
JSON output contains no unresolved values and has non-empty top-level keys: technical_review (test_quality), gap_analysis (coverage_gaps), annotation_summary (annotation_health), risk_assessment (scenario_risk_ratings), recommendations (actions)