Test Name: Submit button is disabled when the queue is empty
Feature: Multi-file mode — submit and batch status card
Traceability:
@SHIFT-48
Description: Verifies that a user cannot submit a batch job when no files have been added to the queue.
This Test Verifies:
| Verification Step | What It Checks |
|---|
| Enable multi-file mode |
Multi-file mode can be turned on by the user |
| Submit button is disabled |
The submit action is unavailable when the file queue is empty, preventing accidental empty submissions |
Test Name: Submitting a valid multi-file batch shows the batch status card
Feature: Multi-file mode — submit and batch status card
Traceability:
@SHIFT-51
Description: Verifies that after submitting a batch with at least one file, the user sees a batch status card and the single-file results panel is hidden.
This Test Verifies:
| Verification Step | What It Checks |
|---|
| Select format and role, add a file, click submit |
A complete and valid batch submission can be initiated |
| Batch status card is visible |
The user receives confirmation that their batch job has been submitted |
| Results panel is not visible |
The single-file results area does not interfere with the batch workflow |
Test Name: Batch status card shows the job reference and polling message
Feature: Multi-file mode — submit and batch status card
Traceability:
@SHIFT-51
Description: Verifies that after submitting a batch, the status card displays a unique job reference and a message indicating that results are being processed.
This Test Verifies:
| Verification Step | What It Checks |
|---|
| Batch status card shows a job_id reference |
The user can see a traceable identifier for their submitted batch job |
| Batch status card shows the polling message |
The user is informed that processing is underway and results are not yet ready |
Test Name: Batch status card remains visible after switching back to single-file mode
Feature: Multi-file mode — submit and batch status card
Traceability:
@SHIFT-51
Description: Verifies that the batch status card persists on screen even if the user switches back to single-file mode after submitting a batch.
This Test Verifies:
| Verification Step | What It Checks |
|---|
| Submit batch and then disable multi-file mode |
The user can toggle the mode after submission without losing their batch status |
| Batch status card is still visible |
The submitted batch job status is not lost when the user changes the input mode |
Test Name: Batch status card summary row shows format, role and file count
Feature: Multi-file mode — submit and batch status card
Traceability:
@SHIFT-51
Description: Verifies that the batch status card displays an accurate summary of the submitted job, including the selected format, role, and number of files.
This Test Verifies:
| Verification Step | What It Checks |
|---|
| Batch status card shows the format label |
The user can confirm which file format was used for the batch submission |
| Batch status card shows the role label 'Product Owner' |
The user can confirm which role was selected when the batch was submitted |
| Batch status card shows '1' for file count |
The user can see exactly how many files were included in the batch job |
Test Name: Submit button is disabled when the queue is empty
Feature: Multi-file mode — submit and batch status card
Traceability:
@SHIFT-48
Execution:
Tag: @requires_login
Journey: A logged-in user enables multi-file mode and sees the submit button disabled when no files have been added to the queue.
| Scenario |
Given Context |
When Action |
Then Assertion |
Gherkin Type |
|
Submit button is disabled when the queue is empty
|
Analysis and multi-file APIs are mocked; user is on the Analyze page
|
User enables multi-file mode
|
The submit button is disabled
|
Negative
|
Test Name: Submitting a valid multi-file batch shows the batch status card
Feature: Multi-file mode — submit and batch status card
Traceability:
@SHIFT-51
Execution:
Tag: @requires_login
Journey: A logged-in user enables multi-file mode, configures format and role, adds a file, submits the batch, and verifies the batch status card appears while the results panel remains hidden.
| Scenario |
Given Context |
When Action |
Then Assertion |
Gherkin Type |
|
Submitting a valid multi-file batch shows the batch status card
|
Analysis and multi-file APIs are mocked; user is on the Analyze page
|
User enables multi-file mode, selects format 'bdd' and role 'Product Owner', adds a fixture file, and clicks submit
|
The batch status card is visible and the results panel is not visible
|
Positive
|
Test Name: Batch status card shows the job reference and polling message
Feature: Multi-file mode — submit and batch status card
Traceability:
@SHIFT-51
Execution:
Tag: @requires_login
Journey: A logged-in user submits a valid multi-file batch and verifies that the resulting batch status card displays both a job ID reference and a polling status message.
| Scenario |
Given Context |
When Action |
Then Assertion |
Gherkin Type |
|
Batch status card shows the job reference and polling message
|
Analysis and multi-file APIs are mocked; user is on the Analyze page
|
User enables multi-file mode, selects format 'bdd' and role 'Product Owner', adds a fixture file, and clicks submit
|
The batch status card is visible, shows a job_id reference, and shows the polling message
|
Positive
|
Test Name: Batch status card remains visible after switching back to single-file mode
Feature: Multi-file mode — submit and batch status card
Traceability:
@SHIFT-51
Execution:
Tag: @requires_login
Journey: A logged-in user submits a multi-file batch, then switches back to single-file mode, and verifies the batch status card persists and is not dismissed by the mode toggle.
| Scenario |
Given Context |
When Action |
Then Assertion |
Gherkin Type |
|
Batch status card remains visible after switching back to single-file mode
|
Analysis and multi-file APIs are mocked; user is on the Analyze page; a batch has been submitted and the status card is visible
|
User disables multi-file mode
|
The batch status card is still visible
|
Edge Case
|
Test Name: Batch status card summary row shows format, role and file count
Feature: Multi-file mode — submit and batch status card
Traceability:
@SHIFT-51
Execution:
Tag: @requires_login
Journey: A logged-in user submits a single-file multi-file batch and verifies that the batch status card summary row accurately reflects the selected format, role, and a file count of one.
| Scenario |
Given Context |
When Action |
Then Assertion |
Gherkin Type |
|
Batch status card summary row shows format, role and file count
|
Analysis and multi-file APIs are mocked; user is on the Analyze page
|
User enables multi-file mode, selects format 'bdd' and role 'Product Owner', adds one fixture file, and clicks submit
|
The batch status card shows the format label, the role label 'Product Owner', and a file count of '1'
|
Positive
|