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 a valid, fully resolved JSON documentation output containing at least one named test.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The system produces visible output after analyzing the uploaded test file
JSON output has no unresolved values
All fields in the downloaded JSON are populated — no placeholders or missing data remain
JSON has 1 or more tests
At least one test entry is present in the output for a single uploaded test case
Every test has a non-empty test_name
Each documented test is identifiable by a meaningful 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 the output expanded into one separate test entry per data row, yielding three or more documented tests.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The system produces visible output after analyzing the data-driven test file
JSON output has no unresolved values
All fields in the downloaded JSON are fully populated with no placeholders
JSON has 3 or more tests
Data rows are each expanded into individual test entries rather than collapsed into one
Every test has a non-empty test_name
Each expanded test variant is identifiable by a meaningful 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 a valid JSON output where each test 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 analyzing the uploaded test file
JSON output has no unresolved values
All fields in the downloaded JSON are fully populated with no placeholders
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 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, providing traceability detail not present in the Product Owner view
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 the output collapsed into a single test entry whose coverage matrix rows represent each data example using the correct schema.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The system produces visible output after analyzing the data-driven test file
JSON output has no unresolved values
All fields in the downloaded JSON are fully populated with no placeholders
JSON has exactly 1 test
Data-driven tests are collapsed into a single logical test entry in the QA Manager view, contrasting with the Product Owner expansion behavior
Every test has a non-empty test_name
The collapsed test entry is identifiable by a meaningful name
Coverage matrix row count matches the examples
Each data row from the DataProvider is represented as a distinct row in the coverage matrix
Coverage matrix rows use the correct schema for generic
Each coverage matrix row conforms to the expected data structure for generic-type test documentation
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 is populated; 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 named 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 is populated; 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.
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 is populated; 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 collapse into a single named test whose coverage matrix rows match the example count and conform to the generic schema.
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 is populated; downloaded JSON has no unresolved values, contains exactly 1 test, that test has a non-empty test_name, coverage matrix row count matches the DataProvider examples, and all coverage matrix rows use the correct generic schema