Description:Verifies that a completed analysis can be downloaded in Markdown, HTML, and JSON formats, each producing a valid and correctly structured file.
This Test Verifies:
Verification Step
What It Checks
Markdown download
A .md file is downloaded and contains expected Markdown heading syntax
HTML download
A .html file is downloaded and contains valid opening and closing HTML tags
JSON download structure
A .json file is downloaded with the framework set to 'bdd' in the metadata
JSON download content
The JSON file contains at least one test entry
Test Name:JSON download contains add-on sections when add-ons were selected
Journey:A user with a completed BDD Product Owner analysis downloads results in Markdown, HTML, and JSON formats and verifies each file is structurally valid.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
All download formats produce valid output
A completed BDD Product Owner analysis exists
User clicks Download Markdown, then Download HTML, then Download JSON
Each format produces a correctly typed file with expected structural markers: '##' in Markdown, '<html lang=' and '</html>' in HTML, framework 'bdd' metadata and at least one test in JSON
Positive
Test Name:JSON download contains add-on sections when add-ons were selected
Journey:A user who ran a BDD Product Owner analysis with Gap Analysis enabled downloads the JSON output and verifies the add-on section is present at the top level.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
JSON download contains add-on sections when add-ons were selected
A completed BDD Product Owner analysis with Gap Analysis add-on selected
User clicks Download JSON
The downloaded JSON file contains a top-level key 'gap_analysis'