Test Name: Adding more than the maximum files shows a warning toast and rejects the file
Feature: Multi-file mode — file limits and validation
Traceability:
@SHIFT-50
Description: Verifies that attempting to add a file beyond the maximum queue limit is blocked and the user is notified with a warning.
This Test Verifies:
| Verification Step | What It Checks |
|---|
| Fill queue to maximum and attempt to add another file |
The system prevents adding files beyond the maximum allowed limit |
| Warning toast appears |
The user receives a visible notification explaining the file limit has been reached |
| Queue file count does not increase |
The rejected file is not added to the queue |
Test Name: Adding two files when one slot remains toasts and accepts only the first
Feature: Multi-file mode — file limits and validation
Traceability:
@SHIFT-50
Description: Verifies that when only one queue slot remains and two files are added simultaneously, the system accepts the first file, rejects the second, and notifies the user.
This Test Verifies:
| Verification Step | What It Checks |
|---|
| Fill queue to 19 files and attempt to add 2 at once |
The system handles partial acceptance when the batch addition would exceed the limit |
| Warning toast appears |
The user is informed that the file limit was hit during the batch upload |
| Queue shows 20 files |
Exactly one of the two files was accepted, filling the queue to its maximum |
Test Name: A file with no test cases shows an error badge at selection time
Feature: Multi-file mode — file limits and validation
Traceability:
@SHIFT-50
Description: Verifies that a BDD file containing no test cases is immediately flagged with an error badge and a descriptive message when added to the queue.
This Test Verifies:
| Verification Step | What It Checks |
|---|
| Add a BDD fixture file with no scenarios |
The system detects that the file contains no test cases at the point of selection |
| File row shows an error badge |
The user can clearly see which file in the queue is invalid |
| Error message mentions 'No test cases found' |
The user receives a clear explanation of why the file is invalid |
Test Name: A file in the wrong format shows a warning badge at selection time
Feature: Multi-file mode — file limits and validation
Traceability:
@SHIFT-50
Description: Verifies that adding a file whose format does not match the selected analysis format results in a warning badge on that file's queue entry.
This Test Verifies:
| Verification Step | What It Checks |
|---|
| Select BDD format and add a Playwright spec file |
The system detects a mismatch between the selected analysis format and the file's actual format |
| File row shows a warning badge |
The user is alerted that the file may not be compatible with the chosen analysis format |
Test Name: A file that exceeds the size limit shows an error badge at selection time
Feature: Multi-file mode — file limits and validation
Traceability:
@SHIFT-50
Description: Verifies that a file exceeding the allowed size limit is immediately flagged with an error badge and a descriptive message when added to the queue.
This Test Verifies:
| Verification Step | What It Checks |
|---|
| Add an oversized file to the queue |
The system detects that the file exceeds the permitted size at the point of selection |
| File row shows an error badge |
The user can clearly see which file in the queue is too large |
| Error message mentions 'File too large' |
The user receives a clear explanation of why the file was rejected |
Test Name: A valid file shows an ok badge
Feature: Multi-file mode — file limits and validation
Traceability:
@SHIFT-50
Description: Verifies that a well-formed BDD file matching the selected analysis format is accepted and shown with a positive status badge in the queue.
This Test Verifies:
| Verification Step | What It Checks |
|---|
| Select BDD format and add a valid BDD fixture file |
The system correctly identifies the file as valid for the chosen analysis format |
| File row shows an ok badge |
The user receives clear confirmation that the file is ready for analysis |
Test Name: Adding more than the maximum files shows a warning toast and rejects the file
Feature: Multi-file mode — file limits and validation
Traceability:
@SHIFT-50
Execution:
Tag: @requires_login
Journey: A user who has already filled the queue to the maximum limit attempts to add one more file and is blocked with a warning toast, confirming the hard cap is enforced.
| Scenario |
Given Context |
When Action |
Then Assertion |
Gherkin Type |
|
Adding more than the maximum files shows a warning toast and rejects the file
|
Multi-file mode is enabled and the queue is at the maximum file limit
|
User attempts to add another file to the queue
|
A warning toast about the file limit is shown and the queue file count does not increase
|
Boundary
|
Test Name: Adding two files when one slot remains toasts and accepts only the first
Feature: Multi-file mode — file limits and validation
Traceability:
@SHIFT-50
Execution:
Tag: @requires_login
Journey: A user with one slot remaining in the queue attempts to add two files simultaneously; only the first is accepted, the second is rejected with a warning toast, verifying partial-batch boundary enforcement.
| Scenario |
Given Context |
When Action |
Then Assertion |
Gherkin Type |
|
Adding two files when one slot remains toasts and accepts only the first
|
Multi-file mode is enabled and the queue contains 19 files (one slot remaining)
|
User attempts to add 2 files at once
|
A warning toast about the file limit is shown and the queue shows exactly 20 files
|
Boundary
|
Test Name: A file with no test cases shows an error badge at selection time
Feature: Multi-file mode — file limits and validation
Traceability:
@SHIFT-50
Execution:
Tag: @requires_login
Journey: A user selects BDD format and adds a feature file that contains no scenarios; the queue immediately flags the file with an error badge and a descriptive message, preventing silent submission of empty files.
| Scenario |
Given Context |
When Action |
Then Assertion |
Gherkin Type |
|
A file with no test cases shows an error badge at selection time
|
Multi-file mode is enabled and analysis format is set to BDD
|
User adds fixture 'bdd_no_scenarios.feature' to the queue
|
The file row shows an error badge and the error message mentions 'No test cases found'
|
Negative
|
Test Name: A file in the wrong format shows a warning badge at selection time
Feature: Multi-file mode — file limits and validation
Traceability:
@SHIFT-50
Execution:
Tag: @requires_login
Journey: A user selects BDD format but adds a Playwright TypeScript spec file; the queue immediately flags the format mismatch with a warning badge, alerting the user before any analysis is triggered.
| Scenario |
Given Context |
When Action |
Then Assertion |
Gherkin Type |
|
A file in the wrong format shows a warning badge at selection time
|
Multi-file mode is enabled and analysis format is set to BDD
|
User adds fixture 'playwright_single_sample.spec.ts' to the queue
|
The file row for 'playwright_single_sample.spec.ts' shows a warning badge
|
Negative
|
Test Name: A file that exceeds the size limit shows an error badge at selection time
Feature: Multi-file mode — file limits and validation
Traceability:
@SHIFT-50
Execution:
Tag: @requires_login
Journey: A user adds a file that exceeds the allowed size limit; the queue immediately rejects it with an error badge and a 'File too large' message, enforcing the upload size constraint at selection time.
| Scenario |
Given Context |
When Action |
Then Assertion |
Gherkin Type |
|
A file that exceeds the size limit shows an error badge at selection time
|
Multi-file mode is enabled
|
User adds an oversized file to the queue
|
The file row shows an error badge and the error message mentions 'File too large'
|
Boundary
|
Test Name: A valid file shows an ok badge
Feature: Multi-file mode — file limits and validation
Traceability:
@SHIFT-50
Execution:
Tag: @requires_login
Journey: A user selects BDD format and adds a well-formed feature file; the queue immediately confirms the file is valid by displaying an ok badge, providing positive feedback before submission.
| Scenario |
Given Context |
When Action |
Then Assertion |
Gherkin Type |
|
A valid file shows an ok badge
|
Multi-file mode is enabled and analysis format is set to BDD
|
User adds fixture 'bdd_sample.feature' to the queue
|
The file row for 'bdd_sample.feature' shows an ok badge
|
Positive
|