Test Name:Submitting a multi-file batch returns 202 Accepted
Feature:Multi-file batch processing and email delivery
Traceability:@SHIFT-51
Description:Verifies that when a Product Owner submits multiple files for batch analysis, the system accepts the request and confirms it is being processed.
This Test Verifies:
Verification Step
What It Checks
Enable multi-file mode and queue two files
The user can add multiple files to a batch submission queue
Click the submit button
The batch submission can be triggered by the user
Batch status card appears
The user receives visible confirmation that their batch is being processed
Backend accepted the request with status 202
The system correctly acknowledges the batch request as accepted for async processing
Test Name:A multifile_batch_complete event is logged after the batch completes
Feature:Multi-file batch processing and email delivery
Traceability:@SHIFT-52
Description:Verifies that completing a multi-file batch submission generates a usage log event with a valid processing time, supporting analytics and monitoring.
This Test Verifies:
Verification Step
What It Checks
Submit a single-file batch
A minimal batch submission triggers the completion event flow
A multifile_batch_complete usage log event is recorded
The system logs a completion event for auditing and usage tracking purposes
The event has a positive processing_ms value
The logged event captures a meaningful processing duration, confirming timing data is recorded
Test Name:Batch status card transitions to complete state after processing finishes
Feature:Multi-file batch processing and email delivery
Traceability:@SHIFT-51
Description:Verifies that the batch status card progresses from a processing state to a completion state and notifies the user that results have been emailed.
This Test Verifies:
Verification Step
What It Checks
Batch status card shown in polling state
The user can see that their batch is actively being processed after submission
Wait for batch status card to show completion
The status card updates automatically when processing finishes without requiring user action
Batch status card shows 'Results emailed'
The user is clearly informed that their results have been delivered to their email
Test Name:Batch status card can be dismissed after completion
Feature:Multi-file batch processing and email delivery
Traceability:@SHIFT-51
Description:Verifies that once batch processing is complete, the user can dismiss the status card to clean up their workspace.
This Test Verifies:
Verification Step
What It Checks
Wait for batch status card to show completion
The dismiss option is only available after the batch has fully completed
Click the dismiss button on the batch status card
The user can actively remove the status card from view
Batch status card is not visible
The card is fully removed from the page after dismissal, keeping the interface uncluttered
Test Name:Submitting a multi-file batch returns 202 Accepted
Feature:Multi-file batch processing and email delivery
Traceability:@SHIFT-51
Execution:Tag: @requires_login
Journey:A user submits a multi-file batch with two fixtures and verifies the backend acknowledges the request with HTTP 202 Accepted and displays a batch status card.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Submitting a multi-file batch returns 202 Accepted
User is on the Analyze page
User enables multi-file mode, selects format and role, adds two fixture files to the queue, and submits
Batch status card is visible and backend responded with status 202
Positive
Test Name:A multifile_batch_complete event is logged after the batch completes
Feature:Multi-file batch processing and email delivery
Traceability:@SHIFT-52
Execution:Tag: @requires_login
Journey:A user submits a single-file batch and verifies that a usage log event of type 'multifile_batch_complete' is recorded with a positive processing duration.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
A multifile_batch_complete event is logged after the batch completes
User is on the Analyze page
User enables multi-file mode, selects format and role, adds one fixture file, and submits
A 'multifile_batch_complete' usage log event is recorded with a positive processing_ms value
Positive
Test Name:Batch status card transitions to complete state after processing finishes
Feature:Multi-file batch processing and email delivery
Traceability:@SHIFT-51
Execution:Tag: @requires_login
Journey:A user submits a batch and observes the status card moving through a polling state before settling on a completion state that confirms results were emailed.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Batch status card transitions to complete state after processing finishes
User is on the Analyze page
User enables multi-file mode, selects format and role, adds one fixture file, and submits
Status card first shows polling state, then transitions to completion state displaying 'Results emailed'
Positive
Test Name:Batch status card can be dismissed after completion
Feature:Multi-file batch processing and email delivery
Traceability:@SHIFT-51
Execution:Tag: @requires_login
Journey:A user submits a batch, waits for it to complete, then dismisses the status card and verifies it is no longer visible.
Scenario
Given Context
When Action
Then Assertion
Gherkin Type
Batch status card can be dismissed after completion
User is on the Analyze page with a completed batch status card visible
User clicks the dismiss button on the batch status card
The batch status card is no longer visible on the page