Test Name:Annotation Summary renders and JSON is complete for QA Manager
Feature:Annotation Summary UI
User Role:QA Manager
Traceability:@SHIFT-27@SHIFT-28
Description:Verifies that a QA Manager can upload a BDD test file, trigger analysis with the Annotation Summary add-on, and receive a complete output — both on screen and as a downloadable JSON — that includes a fully populated Annotation Health section without any missing or unresolved values.
This Test Verifies:
Verification Step
What It Checks
Documentation and analysis appears in the output panel
The analysis result is visible to the user after processing
"Annotation Health" appears exactly once in the output content
The Annotation Health section is present without duplication in the on-screen output
The downloaded JSON output has no unresolved values
All fields in the exported JSON are fully populated with no placeholders or missing data
The JSON has a top-level key "annotation_summary"
The exported JSON is structured correctly with the expected root section
The "annotation_summary" section has a non-empty "annotation_health"
The Annotation Health data is present and contains content in the JSON export
"annotation_health" appears exactly once inside "annotation_summary"
The JSON structure is clean with no duplicate keys or sections
Test Name:Annotation Summary renders and JSON is complete for Product Owner
Feature:Annotation Summary UI
User Role:Product Owner
Traceability:@SHIFT-27@SHIFT-28
Description:Verifies that a Product Owner can upload a BDD test file, trigger analysis with the Annotation Summary add-on, and receive a complete output — both on screen and as a downloadable JSON — that includes a fully populated Annotation Health section without any missing or unresolved values.
This Test Verifies:
Verification Step
What It Checks
Documentation and analysis appears in the output panel
The analysis result is visible to the user after processing
"Annotation Health" appears exactly once in the output content
The Annotation Health section is present without duplication in the on-screen output
The downloaded JSON output has no unresolved values
All fields in the exported JSON are fully populated with no placeholders or missing data
The JSON has a top-level key "annotation_summary"
The exported JSON is structured correctly with the expected root section
The "annotation_summary" section has a non-empty "annotation_health"
The Annotation Health data is present and contains content in the JSON export
"annotation_health" appears exactly once inside "annotation_summary"
The JSON structure is clean with no duplicate keys or sections
Test Name:Annotation Summary renders and JSON is complete for <role>
Feature:Annotation Summary UI
Type:Scenario Outline
Traceability:@SHIFT-27@SHIFT-28
Journey:A user selects the Annotation Summary add-on for a BDD fixture file and verifies that the output panel renders exactly one Annotation Health section and the downloaded JSON is structurally complete with no unresolved values.