Description:Verifies that uploading a BDD feature file and generating documentation produces a well-formed JSON output containing named tests, descriptions, and coverage details.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The user sees generated documentation after submitting a BDD file
JSON output has no unresolved values
No placeholder or missing values exist in the downloaded output
JSON has 1 or more tests
At least one test entry is produced from the uploaded file
Every test has a non-empty test_name
Each test in the output is identifiable by name
First test has a non-empty description
The output includes a human-readable description for the first test
First test has a non-empty test_coverage array
Coverage details are populated for the first test
Test Name:BDD - PO - data-driven produces multiple tests
Feature:BDD Analysis
User Role:Product Owner
Traceability:@SHIFT-19
Description:Verifies that uploading a data-driven BDD feature file generates a separate test entry for each data row, resulting in multiple documented tests.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The user sees generated documentation after submitting a data-driven BDD file
JSON output has no unresolved values
No placeholder or missing values exist in the downloaded output
JSON has 3 or more tests
Multiple test entries are produced, reflecting the parameterised nature of the file
Every test has a non-empty test_name
Each generated test entry is identifiable by name
Test Name:Panel title is "Documentation" when no add-ons are selected
Feature:BDD Analysis
User Role:Product Owner
Traceability:@SHIFT-21
Description:Verifies that the output panel displays the title 'Documentation' rather than an extended title when no additional analysis options are selected.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The user sees output after submitting a BDD file with no add-ons
Panel title is not 'Documentation and Analysis'
The panel heading accurately reflects that only documentation — not analysis — was requested
Test Name:BDD - QAM - coverage matrix populated
Feature:BDD Analysis
User Role:QA Manager
Traceability:@SHIFT-18
Description:Verifies that a QA Manager uploading a BDD feature file receives documentation that includes a correctly structured coverage matrix for each test.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The user sees generated documentation after submitting the file
Filename appears in output
The output references the uploaded file by name, confirming the correct file was processed
JSON output has no unresolved values
No placeholder or missing values exist in the downloaded output
First test has a non-empty test_coverage_matrix array
A coverage matrix is present and populated for the first test
Coverage matrix rows use the correct schema for BDD
Each row in the matrix conforms to the expected structure for BDD-format files
Test Name:BDD - PO - core output structure
Feature:BDD Analysis
Traceability:@SHIFT-17
Journey:A Product Owner uploads a BDD feature fixture and documents test cases, verifying the JSON output is structurally valid with named tests and coverage data.
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 fixture and verifies the output 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+ 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 with no add-ons selected and verifies the output panel title is 'Documentation' rather than 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 fixture and verifies the JSON output includes a correctly structured coverage matrix with BDD-specific schema per test.
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 is populated and shows the filename; downloaded JSON has no unresolved values, the first test has a non-empty test_coverage_matrix array, and each coverage matrix row conforms to the BDD schema