Test Name:Selenium - PO - single test, core output structure
Feature:Selenium Analysis
Traceability:@SHIFT-17
Description:Verifies that a Product Owner uploading a single Selenium test receives valid, complete documentation with at least one named test in the output.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The system produces visible output after processing a single Selenium test file
JSON output has no unresolved values
All fields in the downloaded output are fully populated with no placeholders or missing data
JSON has 1 or more tests
At least one test entry is present in the output
Every test has a non-empty test_name
Each documented test is identifiable by name
Test Name:Selenium - PO - Parameterized expands one test per row
Feature:Selenium Analysis
Traceability:@SHIFT-19
Description:Verifies that a Product Owner uploading a data-driven Selenium test sees each data row expanded into its own separate test entry 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 Selenium test file
JSON output has no unresolved values
All fields in the downloaded output are fully populated with no placeholders or missing data
JSON has 3 or more tests
Each data row in the parameterized test is expanded into its own test entry, resulting in multiple tests
Every test has a non-empty test_name
Each expanded test entry is identifiable by name
Test Name:Selenium - QAM - single test, coverage matrix populated
Feature:Selenium Analysis
Traceability:@SHIFT-18
Description:Verifies that a QA Manager uploading a single Selenium test receives documentation that includes a populated test coverage matrix.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The system produces visible output after processing a single Selenium test file
JSON output has no unresolved values
All fields in the downloaded output are fully populated with no placeholders or missing data
JSON has 1 or more tests
At least one test entry is present in the output
Every test has a non-empty test_name
Each documented test is identifiable by name
First test has a non-empty array test_coverage_matrix
The QA Manager view includes a coverage matrix with at least one entry for the test
Test Name:Selenium - QAM - Parameterized collapses
Feature:Selenium Analysis
Traceability:@SHIFT-20
Description:Verifies that a QA Manager uploading a data-driven Selenium test sees all data rows collapsed into a single test entry with a coverage matrix row for each example.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The system produces visible output after processing a data-driven Selenium test file
JSON output has no unresolved values
All fields in the downloaded output are fully populated with no placeholders or missing data
JSON has exactly 1 test
All data rows are collapsed into a single test entry rather than expanded
Every test has a non-empty test_name
The collapsed test entry is identifiable by name
Coverage matrix row count matches the examples
Each data row from the parameterized test is represented as a separate row in the coverage matrix
Coverage matrix rows use the correct schema for generic
Each coverage matrix row conforms to the expected structure for generic test types
Test Name:Selenium - PO - single test, core output structure
Feature:Selenium Analysis
Traceability:@SHIFT-17
Journey:A Product Owner uploads a single Selenium test fixture and verifies that the analysis produces valid, fully-resolved JSON output containing at least one named test.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Selenium - PO - single test, core output structure
User is on the Analyze page
Selects format 'selenium' and role 'Product Owner', uploads 'selenium_single_sample.java', and clicks 'Document test cases'
Output panel shows documentation; downloaded JSON has no unresolved values, contains 1 or more tests, and every test has a non-empty test_name
Positive
Test Name:Selenium - PO - Parameterized expands one test per row
Feature:Selenium Analysis
Traceability:@SHIFT-19
Journey:A Product Owner uploads a data-driven Selenium fixture and verifies that the analysis expands parameterized tests so the JSON output contains one entry per data row (3 or more tests).
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Selenium - PO - Parameterized expands one test per row
User is on the Analyze page
Selects format 'selenium' and role 'Product Owner', uploads 'selenium_datadriven_sample.java', and clicks 'Document test cases'
Output panel shows documentation; downloaded JSON has no unresolved values, contains 3 or more tests, and every test has a non-empty test_name
Positive
Test Name:Selenium - QAM - single test, coverage matrix populated
Feature:Selenium Analysis
Traceability:@SHIFT-18
Journey:A QA Manager uploads a single Selenium test fixture and verifies that the analysis produces valid JSON output where the first test includes a populated test_coverage_matrix array.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Selenium - QAM - single test, coverage matrix populated
User is on the Analyze page
Selects format 'selenium' and role 'QA Manager', uploads 'selenium_single_sample.java', and clicks 'Document test cases'
Output panel shows documentation; downloaded JSON has no unresolved values, 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:Selenium - QAM - Parameterized collapses
Feature:Selenium Analysis
Traceability:@SHIFT-20
Journey:A QA Manager uploads a data-driven Selenium fixture and verifies that the analysis collapses parameterized tests into exactly one test entry whose coverage matrix rows match the number of data examples and conform to the generic schema.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Selenium - QAM - Parameterized collapses
User is on the Analyze page
Selects format 'selenium' and role 'QA Manager', uploads 'selenium_datadriven_sample.java', and clicks 'Document test cases'
Output panel shows documentation; downloaded JSON has no unresolved values, contains exactly 1 test, every test has a non-empty test_name, coverage matrix row count matches the examples, and rows use the correct generic schema