Test Name:Swift - PO - single test, core output structure
Feature:Swift Analysis
User Role:Product Owner
Traceability:@SHIFT-17
Description:Verifies that uploading a single Swift test file produces valid, well-formed documentation output with at least one named test case.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The tool produces visible output after processing a Swift file
JSON output has no unresolved values
All placeholders or template tokens in the output are fully resolved
JSON framework is 'swift'
The output correctly identifies the source language as Swift
JSON has 1 or more tests
At least one test case is detected and documented from the uploaded file
Every test has a non-empty test_name
Each documented test case is assigned a meaningful name
Test Name:Swift - PO - struct+for data-driven expands one test per row
Feature:Swift Analysis
User Role:Product Owner
Traceability:@SHIFT-19
Description:Verifies that a data-driven Swift test using struct and for-loop patterns is expanded into one documented test entry per data row.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The tool produces visible output after processing a data-driven Swift file
JSON output has no unresolved values
All placeholders or template tokens in the output are fully resolved
JSON framework is 'swift'
The output correctly identifies the source language as Swift
JSON has 3 or more tests
Data-driven rows are each expanded into their own separate test entry, yielding at least 3 tests
Every test has a non-empty test_name
Each expanded test case is assigned a meaningful name
Test Name:Swift - QAM - single test, coverage matrix populated
Feature:Swift Analysis
User Role:QA Manager
Traceability:@SHIFT-18
Description:Verifies that when a QA Manager analyzes a single Swift test file, the output includes a populated test coverage matrix for each test case.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The tool produces visible output after processing a Swift file
JSON output has no unresolved values
All placeholders or template tokens in the output are fully resolved
JSON framework is 'swift'
The output correctly identifies the source language as Swift
JSON has 1 or more tests
At least one test case is detected and documented from the uploaded file
Every test has a non-empty test_name
Each documented test case is assigned a meaningful name
First test has a non-empty array test_coverage_matrix
The QA Manager role triggers generation of a coverage matrix with at least one entry
Test Name:Swift - QAM - data-driven collapses
Feature:Swift Analysis
User Role:QA Manager
Traceability:@SHIFT-20
Description:Verifies that when a QA Manager analyzes a data-driven Swift test file, the multiple data rows are collapsed into a single test entry whose coverage matrix rows match the number of examples and follow the correct schema.
This Test Verifies:
Verification Step
What It Checks
Documentation appears in output panel
The tool produces visible output after processing a data-driven Swift file
JSON output has no unresolved values
All placeholders or template tokens in the output are fully resolved
JSON framework is 'swift'
The output correctly identifies the source language as Swift
JSON has exactly 1 test
Data-driven rows are collapsed into a single test entry under the QA Manager role
Every test has a non-empty test_name
The collapsed test case is assigned a meaningful name
Coverage matrix row count matches the examples
The number of rows in the coverage matrix equals the number of data-driven input rows
Coverage matrix rows use the correct schema for 'swift'
Each coverage matrix row conforms to the expected Swift-specific structure
Test Name:Swift - PO - single test, core output structure
Feature:Swift Analysis
Traceability:@SHIFT-17
Journey:A Product Owner uploads a single Swift 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
Swift - PO - single test, core output structure
User is on the Analyze page
Selects format 'swift' and role 'Product Owner', uploads 'swift_single_sample.swift', and clicks 'Document test cases'
Output panel is populated; downloaded JSON has no unresolved values, framework is 'swift', contains 1 or more tests, and every test has a non-empty test_name
Positive
Test Name:Swift - PO - struct+for data-driven expands one test per row
Feature:Swift Analysis
Traceability:@SHIFT-19
Journey:A Product Owner uploads a data-driven Swift fixture and verifies that the analyser expands struct+for loops into individual tests, producing at least three distinct named test entries in the JSON output.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Swift - PO - struct+for data-driven expands one test per row
User is on the Analyze page
Selects format 'swift' and role 'Product Owner', uploads 'swift_datadriven_sample.swift', and clicks 'Document test cases'
Output panel is populated; downloaded JSON has no unresolved values, framework is 'swift', contains 3 or more tests, and every test has a non-empty test_name
Positive
Test Name:Swift - QAM - single test, coverage matrix populated
Feature:Swift Analysis
Traceability:@SHIFT-18
Journey:A QA Manager uploads a single Swift test fixture and verifies that the analysis returns valid JSON with a fully populated coverage matrix on the first test.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Swift - QAM - single test, coverage matrix populated
User is on the Analyze page
Selects format 'swift' and role 'QA Manager', uploads 'swift_single_sample.swift', and clicks 'Document test cases'
Output panel is populated; downloaded JSON has no unresolved values, framework is 'swift', 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:Swift - QAM - data-driven collapses
Feature:Swift Analysis
Traceability:@SHIFT-20
Journey:A QA Manager uploads a data-driven Swift fixture and verifies that the analyser collapses all data rows into a single test entry whose coverage matrix rows match the number of examples and conform to the Swift schema.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Swift - QAM - data-driven collapses
User is on the Analyze page
Selects format 'swift' and role 'QA Manager', uploads 'swift_datadriven_sample.swift', and clicks 'Document test cases'
Output panel is populated; downloaded JSON has no unresolved values, framework is 'swift', contains exactly 1 test, every test has a non-empty test_name, coverage matrix row count matches the data-driven examples, and coverage matrix rows use the correct Swift schema