Test Name:Appium - PO - single test, core output structure
Feature:Appium Analysis
Traceability:@SHIFT-17
Description:Verifies that a Product Owner uploading a single Appium test file receives documented output with at least one named test case.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The system produces visible output after analyzing the uploaded file
JSON output has no unresolved values
All fields in the output are fully populated with no placeholders or nulls
JSON has 1 or more tests
At least one test case is extracted from the uploaded file
Every test has a non-empty test_name
Each documented test case is identifiable by name
Test Name:Appium - PO - DataProvider expands one test per row
Feature:Appium Analysis
Traceability:@SHIFT-19
Description:Verifies that a Product Owner uploading a data-driven Appium test file sees each data row expanded into its own separate test case in the output.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The system produces visible output after analyzing the data-driven file
JSON output has no unresolved values
All fields in the output are fully populated with no placeholders or nulls
JSON has 3 or more tests
Each data row in the DataProvider is expanded into its own test entry
Every test has a non-empty test_name
Each expanded test case is identifiable by name
Test Name:Appium - QAM - single test, coverage matrix populated
Feature:Appium Analysis
Traceability:@SHIFT-18
Description:Verifies that a QA Manager uploading a single Appium test file receives output that includes a populated test coverage matrix alongside standard test documentation.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The system produces visible output after analyzing the uploaded file
JSON output has no unresolved values
All fields in the output are fully populated with no placeholders or nulls
JSON has 1 or more tests
At least one test case is extracted from the uploaded file
Every test has a non-empty test_name
Each documented test case 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:Appium - QAM - DataProvider collapses
Feature:Appium Analysis
Traceability:@SHIFT-20
Description:Verifies that a QA Manager uploading a data-driven Appium test file sees all data rows collapsed into a single test entry whose coverage matrix reflects each data row individually.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The system produces visible output after analyzing the data-driven file
JSON output has no unresolved values
All fields in the output are fully populated with no placeholders or nulls
JSON has exactly 1 test
Data rows are collapsed into a single test case rather than expanded for the QA Manager role
Every test has a non-empty test_name
The collapsed test case is identifiable by name
Coverage matrix row count matches the examples
Each data row from the DataProvider is represented as its own 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 data-driven tests
Test Name:Appium - PO - single test, core output structure
Feature:Appium Analysis
Traceability:@SHIFT-17
Journey:A Product Owner uploads a single Appium test fixture and verifies that the documentation pipeline produces valid, fully-resolved JSON output containing at least one named test.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Appium - PO - single test, core output structure
User is on the Analyze page
Selects format 'appium' and role 'Product Owner', uploads 'appium_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:Appium - PO - DataProvider expands one test per row
Feature:Appium Analysis
Traceability:@SHIFT-19
Journey:A Product Owner uploads a data-driven Appium fixture and verifies that each DataProvider row is expanded into its own discrete test entry in the JSON output.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Appium - PO - DataProvider expands one test per row
User is on the Analyze page
Selects format 'appium' and role 'Product Owner', uploads 'appium_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:Appium - QAM - single test, coverage matrix populated
Feature:Appium Analysis
Traceability:@SHIFT-18
Journey:A QA Manager uploads a single Appium test fixture and verifies that the JSON output includes a populated test_coverage_matrix on the first test, confirming the QAM-role enrichment pipeline is working.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Appium - QAM - single test, coverage matrix populated
User is on the Analyze page
Selects format 'appium' and role 'QA Manager', uploads 'appium_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:Appium - QAM - DataProvider collapses
Feature:Appium Analysis
Traceability:@SHIFT-20
Journey:A QA Manager uploads a data-driven Appium fixture and verifies that DataProvider rows are collapsed into a single test with a coverage matrix whose row count and schema match the expected data-driven structure.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Appium - QAM - DataProvider collapses
User is on the Analyze page
Selects format 'appium' and role 'QA Manager', uploads 'appium_datadriven_sample.java', and clicks 'Document test cases'
Output panel shows documentation; downloaded JSON has no unresolved values, contains exactly 1 test, test has a non-empty test_name, coverage matrix row count matches the DataProvider examples, and rows conform to the 'generic' schema