Test Name:Cypress - PO - single test, core output structure
Feature:Cypress Analysis
User Role:Product Owner
Traceability:@SHIFT-17
Description:A Product Owner uploading a single Cypress test file receives structured JSON documentation with all fields resolved and at least one named test entry.
This Test Verifies:
Verification Step
What It Checks
Documentation is generated and displayed
The output panel shows results after submitting a single Cypress test file
JSON output has no unresolved values
No placeholder or missing data appears in the downloaded JSON
JSON framework is 'cypress'
The output correctly identifies the test framework as Cypress
JSON has 1 or more tests with non-empty test names
At least one test is documented and each has a meaningful name
Test Name:Cypress - PO - forEach data-driven expands one test per row
Feature:Cypress Analysis
User Role:Product Owner
Traceability:@SHIFT-19
Description:A Product Owner uploading a data-driven Cypress test using forEach sees each data row expanded into its own separate documented test entry.
This Test Verifies:
Verification Step
What It Checks
Documentation is generated and displayed
The output panel shows results after submitting the data-driven forEach Cypress test file
JSON output has no unresolved values
No placeholder or missing data appears in the downloaded JSON
JSON framework is 'cypress'
The output correctly identifies the test framework as Cypress
JSON has 3 or more tests with non-empty test names
Each data row is expanded into a separate test entry, producing at least 3 named tests
Test Name:Cypress - PO - for...of expands one test per row
Feature:Cypress Analysis
User Role:Product Owner
Traceability:@SHIFT-19
Description:A Product Owner uploading a data-driven Cypress test using for...of sees each data row expanded into its own separate documented test entry.
This Test Verifies:
Verification Step
What It Checks
Documentation is generated and displayed
The output panel shows results after submitting the for...of Cypress test file
JSON output has no unresolved values
No placeholder or missing data appears in the downloaded JSON
JSON framework is 'cypress'
The output correctly identifies the test framework as Cypress
JSON has 3 or more tests with non-empty test names
Each data row is expanded into a separate test entry, producing at least 3 named tests
Test Name:Cypress - QAM - single test, coverage matrix populated
Feature:Cypress Analysis
User Role:QA Manager
Traceability:@SHIFT-18
Description:A QA Manager uploading a single Cypress test file receives structured JSON documentation that includes a populated test coverage matrix alongside standard test details.
This Test Verifies:
Verification Step
What It Checks
Documentation is generated and displayed
The output panel shows results after submitting a single Cypress test file
JSON output has no unresolved values
No placeholder or missing data appears in the downloaded JSON
JSON framework is 'cypress'
The output correctly identifies the test framework as Cypress
JSON has 1 or more tests with non-empty test names
At least one test is documented and each has a meaningful name
First test has a non-empty test_coverage_matrix array
The QA Manager view includes a coverage matrix with at least one entry for the test
Test Name:Cypress - QAM - forEach collapses
Feature:Cypress Analysis
User Role:QA Manager
Traceability:@SHIFT-20
Description:A QA Manager uploading a data-driven Cypress test using forEach sees all data rows collapsed into a single test entry with a coverage matrix row for each data example.
This Test Verifies:
Verification Step
What It Checks
Documentation is generated and displayed
The output panel shows results after submitting the data-driven forEach Cypress test file
JSON output has no unresolved values
No placeholder or missing data appears in the downloaded JSON
JSON framework is 'cypress'
The output correctly identifies the test framework as Cypress
JSON has exactly 1 test with a non-empty test name
All data rows are collapsed into a single named test entry rather than expanded
Coverage matrix row count matches the number of examples
Each data row from the forEach loop is represented as a row in the coverage matrix
Coverage matrix rows use the correct schema for 'cypress'
Each coverage matrix row contains the expected fields for a Cypress test
Test Name:Cypress - QAM - for...of collapses
Feature:Cypress Analysis
User Role:QA Manager
Traceability:@SHIFT-20
Description:A QA Manager uploading a data-driven Cypress test using for...of sees all data rows collapsed into a single test entry with a coverage matrix row for each data example.
This Test Verifies:
Verification Step
What It Checks
Documentation is generated and displayed
The output panel shows results after submitting the for...of Cypress test file
JSON output has no unresolved values
No placeholder or missing data appears in the downloaded JSON
JSON framework is 'cypress'
The output correctly identifies the test framework as Cypress
JSON has exactly 1 test with a non-empty test name
All data rows are collapsed into a single named test entry rather than expanded
Coverage matrix row count matches the number of examples
Each data row from the for...of loop is represented as a row in the coverage matrix
Coverage matrix rows use the correct schema for 'cypress'
Each coverage matrix row contains the expected fields for a Cypress test
Test Name:Cypress - PO - single test, core output structure
Feature:Cypress Analysis
Traceability:@SHIFT-17
Journey:A Product Owner uploads a single Cypress test fixture and verifies that the documentation panel renders and the downloaded JSON output is well-formed with at least one named test.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Cypress - PO - single test, core output structure
User is on the Analyze page
Selects format 'cypress' and role 'Product Owner', uploads 'cypress_single_sample.cy.js', and clicks 'Document test cases'
Documentation appears in the output panel; downloaded JSON has no unresolved values, framework is 'cypress', contains 1 or more tests, and every test has a non-empty test_name
Positive
Test Name:Cypress - PO - forEach data-driven expands one test per row
Feature:Cypress Analysis
Traceability:@SHIFT-19
Journey:A Product Owner uploads a forEach data-driven Cypress fixture and verifies that each data row is expanded into its own test entry in the JSON output.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Cypress - PO - forEach data-driven expands one test per row
User is on the Analyze page
Selects format 'cypress' and role 'Product Owner', uploads 'cypress_datadriven_sample.cy.js', and clicks 'Document test cases'
Documentation appears in the output panel; downloaded JSON has no unresolved values, framework is 'cypress', contains 3 or more tests, and every test has a non-empty test_name
Positive
Test Name:Cypress - PO - for...of expands one test per row
Feature:Cypress Analysis
Traceability:@SHIFT-19
Journey:A Product Owner uploads a for...of data-driven Cypress fixture and verifies that each iteration is expanded into its own test entry in the JSON output.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Cypress - PO - for...of expands one test per row
User is on the Analyze page
Selects format 'cypress' and role 'Product Owner', uploads 'cypress_forof_sample.cy.js', and clicks 'Document test cases'
Documentation appears in the output panel; downloaded JSON has no unresolved values, framework is 'cypress', contains 3 or more tests, and every test has a non-empty test_name
Positive
Test Name:Cypress - QAM - single test, coverage matrix populated
Feature:Cypress Analysis
Traceability:@SHIFT-18
Journey:A QA Manager uploads a single Cypress test fixture and verifies that the JSON output is well-formed and includes a populated test_coverage_matrix on the first test.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Cypress - QAM - single test, coverage matrix populated
User is on the Analyze page
Selects format 'cypress' and role 'QA Manager', uploads 'cypress_single_sample.cy.js', and clicks 'Document test cases'
Documentation appears in the output panel; downloaded JSON has no unresolved values, framework is 'cypress', contains 1 or more tests, every test has a non-empty test_name, and the first test has a non-empty test_coverage_matrix array
Positive
Test Name:Cypress - QAM - forEach collapses
Feature:Cypress Analysis
Traceability:@SHIFT-20
Journey:A QA Manager uploads a forEach data-driven Cypress fixture and verifies that all data rows are collapsed into a single test entry whose coverage matrix rows match the example count and conform to the Cypress schema.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Cypress - QAM - forEach collapses
User is on the Analyze page
Selects format 'cypress' and role 'QA Manager', uploads 'cypress_datadriven_sample.cy.js', and clicks 'Document test cases'
Documentation appears in the output panel; downloaded JSON has no unresolved values, framework is 'cypress', contains exactly 1 test, every test has a non-empty test_name, coverage matrix row count matches the examples, and rows conform to the cypress schema
Positive
Test Name:Cypress - QAM - for...of collapses
Feature:Cypress Analysis
Traceability:@SHIFT-20
Journey:A QA Manager uploads a for...of data-driven Cypress fixture and verifies that all iterations are collapsed into a single test entry whose coverage matrix rows match the example count and conform to the Cypress schema.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Cypress - QAM - for...of collapses
User is on the Analyze page
Selects format 'cypress' and role 'QA Manager', uploads 'cypress_forof_sample.cy.js', and clicks 'Document test cases'
Documentation appears in the output panel; downloaded JSON has no unresolved values, framework is 'cypress', contains exactly 1 test, every test has a non-empty test_name, coverage matrix row count matches the examples, and rows conform to the cypress schema