Description:A Product Owner uploading a BDD feature file receives structured documentation with named tests, descriptions, and coverage details in the output panel.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The system produces visible output after processing a BDD feature file
JSON output has no unresolved values
All fields in the downloaded JSON are fully populated with no placeholder or missing values
JSON has 1 or more tests
At least one test entry is generated from the uploaded feature file
Every test has a non-empty test_name
Each test in the output is identifiable by a name
First test has a non-empty description
The first test includes a human-readable description of what it covers
First test has a non-empty test_coverage array
The first test includes at least one coverage detail entry
Test Name:BDD - PO - data-driven produces multiple tests
Feature:BDD Analysis
User Role:Product Owner
Traceability:@SHIFT-19
Description:A Product Owner uploading a data-driven BDD feature file receives separate documentation entries for each data row, resulting in multiple distinct tests in the output.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The system produces visible output after processing a data-driven BDD feature file
JSON output has no unresolved values
All fields in the downloaded JSON are fully populated with no placeholder or missing values
JSON has 3 or more tests
Data-driven scenarios expand into multiple individual test entries (at least 3)
Every test has a non-empty test_name
Each expanded test entry is identifiable by a name
Test Name:Panel title is "Documentation" when no add-ons are selected
Feature:BDD Analysis
User Role:Product Owner
Traceability:@SHIFT-21
Description:When a Product Owner runs documentation without selecting any add-ons, the output panel title shows 'Documentation' rather than a combined label.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The system produces visible output after processing the feature file
Panel title is not 'Documentation and Analysis'
The output panel title reflects only the base documentation mode and does not include add-on labels when none are selected
Test Name:BDD - QAM - coverage matrix populated
Feature:BDD Analysis
User Role:QA Manager
Traceability:@SHIFT-18
Description:A QA Manager uploading a BDD feature file receives documentation that includes a properly structured coverage matrix linking tests to coverage areas.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The system produces visible output after processing the BDD feature file
Filename appears in output
The source file is referenced in the output, confirming the correct file was processed
JSON output has no unresolved values
All fields in the downloaded JSON are fully populated with no placeholder or missing values
First test has a non-empty test_coverage_matrix array
The first test includes at least one coverage matrix entry for QA Manager reporting
Coverage matrix rows use the correct schema for BDD
Each row in the coverage matrix conforms to the expected structure for BDD-format inputs
Test Name:BDD - PO - core output structure
Feature:BDD Analysis
Traceability:@SHIFT-17
Journey:A Product Owner uploads a BDD feature file and verifies that the documentation output is rendered, downloadable, and structurally valid with at least one named test containing a description and coverage array.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
BDD - PO - core output structure
User is on the Analyze page
Selects format 'bdd' and role 'Product Owner', uploads 'bdd_sample.feature', and clicks 'Document test cases'
Output panel is populated; downloaded JSON has no unresolved values, contains 1+ tests, every test has a non-empty test_name, and the first test has a non-empty description and test_coverage array
Positive
Test Name:BDD - PO - data-driven produces multiple tests
Feature:BDD Analysis
Traceability:@SHIFT-19
Journey:A Product Owner uploads a data-driven BDD feature file and verifies that the output correctly expands into three or more individually named tests.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
BDD - PO - data-driven produces multiple tests
User is on the Analyze page
Selects format 'bdd' and role 'Product Owner', uploads 'bdd_datadriven_sample.feature', and clicks 'Document test cases'
Output panel is populated; downloaded JSON has no unresolved values, contains 3 or more tests, and every test has a non-empty test_name
Positive
Test Name:Panel title is "Documentation" when no add-ons are selected
Feature:BDD Analysis
Traceability:@SHIFT-21
Journey:A Product Owner documents a BDD feature file without any add-ons selected and verifies that the output panel title is 'Documentation' and not the combined 'Documentation and Analysis' label.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Panel title is "Documentation" when no add-ons are selected
User is on the Analyze page with no add-ons selected
Selects format 'bdd' and role 'Product Owner', uploads 'bdd_sample.feature', and clicks 'Document test cases'
Output panel is visible and its title is 'Documentation', not 'Documentation and Analysis'
Negative
Test Name:BDD - QAM - coverage matrix populated
Feature:BDD Analysis
Traceability:@SHIFT-18
Journey:A QA Manager uploads a BDD feature file and verifies that the output includes the source filename, a valid downloadable JSON with no unresolved values, and a correctly structured coverage matrix for the BDD format.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
BDD - QAM - coverage matrix populated
User is on the Analyze page
Selects format 'bdd' and role 'QA Manager', uploads 'bdd_sample.feature', and clicks 'Document test cases'
Output panel shows the filename 'bdd_sample.feature'; downloaded JSON has no unresolved values; the first test has a non-empty test_coverage_matrix array whose rows conform to the BDD schema