Test Name: Uploading a test case file with no test cases shows an error toast
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-33
Description: Uploading a BDD file that contains no test cases blocks the user with an error and leaves the input empty.
This Test Verifies:
| Verification Step | What It Checks |
| Upload empty BDD file |
An error notification appears when the uploaded file contains no test cases |
| Test case box is empty |
No content is loaded into the input area when the file has no usable test cases |
Test Name: Uploading a test case file in the wrong format shows a warning toast with suggestion -- bdd, robot_single_sample.robot, doesn't look like a BDD / Gherkin file, Robot Framework
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-33
Description: When a user uploads a file that doesn't match the selected format, a warning is shown with a suggestion of the correct format, while still loading the file content.
This Test Verifies:
| Verification Step | What It Checks |
| Warning toast appears with mismatch phrase |
User is notified that the uploaded file doesn't match the chosen format (BDD) |
| Toast includes format suggestion |
The warning recommends the correct format (Robot Framework) based on the file content |
| Test case box is populated |
Despite the format mismatch, the file content is still loaded so the user can proceed |
Test Name: Uploading a test case file in the wrong format shows a warning toast with suggestion -- robot, playwright_single_sample.spec.ts, doesn't look like a Robot Framework, Playwright
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-33
Description: When a user uploads a file that doesn't match the selected format, a warning is shown with a suggestion of the correct format, while still loading the file content.
This Test Verifies:
| Verification Step | What It Checks |
| Warning toast appears with mismatch phrase |
User is notified that the uploaded file doesn't match the chosen format (Robot Framework) |
| Toast includes format suggestion |
The warning recommends the correct format (Playwright) based on the file content |
| Test case box is populated |
Despite the format mismatch, the file content is still loaded so the user can proceed |
Test Name: Uploading a test case file in the wrong format shows a warning toast with suggestion -- playwright, bdd_sample.feature, doesn't look like a Playwright file, BDD / Gherkin
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-33
Description: When a user uploads a file that doesn't match the selected format, a warning is shown with a suggestion of the correct format, while still loading the file content.
This Test Verifies:
| Verification Step | What It Checks |
| Warning toast appears with mismatch phrase |
User is notified that the uploaded file doesn't match the chosen format (Playwright) |
| Toast includes format suggestion |
The warning recommends the correct format (BDD / Gherkin) based on the file content |
| Test case box is populated |
Despite the format mismatch, the file content is still loaded so the user can proceed |
Test Name: Uploading a test case file in the wrong format shows a warning toast with suggestion -- cypress, bdd_sample.feature, doesn't look like a Cypress file, BDD / Gherkin
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-33
Description: When a user uploads a file that doesn't match the selected format, a warning is shown with a suggestion of the correct format, while still loading the file content.
This Test Verifies:
| Verification Step | What It Checks |
| Warning toast appears with mismatch phrase |
User is notified that the uploaded file doesn't match the chosen format (Cypress) |
| Toast includes format suggestion |
The warning recommends the correct format (BDD / Gherkin) based on the file content |
| Test case box is populated |
Despite the format mismatch, the file content is still loaded so the user can proceed |
Test Name: Uploading a test case file in the wrong format shows a warning toast with suggestion -- swift, playwright_single_sample.spec.ts, doesn't look like a Swift / XCTest, Playwright
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-33
Description: When a user uploads a file that doesn't match the selected format, a warning is shown with a suggestion of the correct format, while still loading the file content.
This Test Verifies:
| Verification Step | What It Checks |
| Warning toast appears with mismatch phrase |
User is notified that the uploaded file doesn't match the chosen format (Swift / XCTest) |
| Toast includes format suggestion |
The warning recommends the correct format (Playwright) based on the file content |
| Test case box is populated |
Despite the format mismatch, the file content is still loaded so the user can proceed |
Test Name: Uploading a test case file in the wrong format shows a warning toast with suggestion -- espresso, bdd_sample.feature, doesn't look like an Espresso, BDD / Gherkin
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-33
Description: When a user uploads a file that doesn't match the selected format, a warning is shown with a suggestion of the correct format, while still loading the file content.
This Test Verifies:
| Verification Step | What It Checks |
| Warning toast appears with mismatch phrase |
User is notified that the uploaded file doesn't match the chosen format (Espresso) |
| Toast includes format suggestion |
The warning recommends the correct format (BDD / Gherkin) based on the file content |
| Test case box is populated |
Despite the format mismatch, the file content is still loaded so the user can proceed |
Test Name: Uploading a valid test case file shows no toast
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-33
Description: Uploading a file that matches the selected format loads the content silently with no warnings or errors.
This Test Verifies:
| Verification Step | What It Checks |
| No toast is displayed |
A correctly matched file upload does not trigger any warning or error notifications |
| Test case box is populated |
The valid file content is successfully loaded into the input area |
Test Name: Pasting content that exceeds the character limit shows an error and does not load the box
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-35
Description: Pasting content that is too long is blocked with a clear error message, preventing oversized input from being submitted.
This Test Verifies:
| Verification Step | What It Checks |
| Paste error shown with 'too long' message |
Users receive a clear error when their pasted content exceeds the allowed character limit |
| Test case box is empty |
Oversized content is rejected and not loaded into the input area |
Test Name: Pasting valid matching content shows no toast
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-34@SHIFT-35
Description: Pasting content that matches the selected format and is within size limits loads cleanly with no warnings or errors.
This Test Verifies:
| Verification Step | What It Checks |
| No toast is displayed |
Valid pasted content does not trigger any warning or error notifications |
| Test case box is populated |
The pasted content is successfully loaded into the input area |
Test Name: Warning toast dismisses and content remains loaded
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-33
Description: After dismissing a format mismatch warning, the uploaded content remains available so the user can continue working.
This Test Verifies:
| Verification Step | What It Checks |
| Warning toast appears on mismatched upload |
A format mismatch triggers a warning notification |
| Toast is dismissed |
The user can manually close the warning notification |
| Test case box is still populated |
Dismissing the warning does not clear the loaded content — the user's work is preserved |
Test Name: Dropping multiple test case files in single-file mode shows a dismissible warning
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-48
Description: Dropping multiple files when the page is in single-file mode shows a helpful warning guiding the user to switch modes, and the warning can be dismissed.
This Test Verifies:
| Verification Step | What It Checks |
| Warning message is visible with multi-file guidance |
Users are clearly informed they need to switch to multi-file mode to upload more than one file at once |
| Dismiss button is visible on the warning |
The warning provides a way for users to close it manually |
| Test case box is empty |
No content is loaded when multiple files are dropped in single-file mode |
| Warning message is no longer visible after dismissal |
Clicking the dismiss button successfully removes the warning from view |
Test Name: Uploading a test case file with no test cases shows an error toast
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-33
Execution:
Tag: @file-validation
Journey: A user uploads a BDD file containing no scenarios and expects an error toast confirming no test cases were found, with the input box remaining empty.
| Scenario |
Given Context |
When Action |
Then Assertion |
Gherkin Type |
|
Uploading a test case file with no test cases shows an error toast
|
Format is set to BDD
|
User uploads a BDD fixture file that contains no scenarios
|
An error toast appears with 'No test cases found' and the test case box is empty
|
Negative
|
Test Name: Uploading a test case file in the wrong format shows a warning toast with suggestion
Feature: Test case file validation on the Analyze page
Type: Scenario Outline
Traceability:
@SHIFT-33
Execution:
Tag: @file-validation
Journey: A user uploads a file whose format does not match the selected parser and expects a warning toast identifying the mismatch and suggesting the correct format, while the file content is still loaded into the input box.
Examples
| Selected Format |
Fixture File |
Mismatch Phrase |
Suggestion |
| bdd |
robot_single_sample.robot |
doesn't look like a BDD / Gherkin file |
Robot Framework |
| robot |
playwright_single_sample.spec.ts |
doesn't look like a Robot Framework |
Playwright |
| playwright |
bdd_sample.feature |
doesn't look like a Playwright file |
BDD / Gherkin |
| cypress |
bdd_sample.feature |
doesn't look like a Cypress file |
BDD / Gherkin |
| swift |
playwright_single_sample.spec.ts |
doesn't look like a Swift / XCTest |
Playwright |
| espresso |
bdd_sample.feature |
doesn't look like an Espresso |
BDD / Gherkin |
Test Name: Uploading a valid test case file shows no toast
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-33
Execution:
Tag: @file-validation
Journey: A user uploads a Playwright file that correctly matches the selected format and expects no toast to appear while the content loads successfully into the input box.
| Scenario |
Given Context |
When Action |
Then Assertion |
Gherkin Type |
|
Uploading a valid test case file shows no toast
|
Format is set to Playwright
|
User uploads a matching Playwright fixture file
|
No toast is displayed and the test case box is populated
|
Positive
|
Test Name: Pasting content that exceeds the character limit shows an error and does not load the box
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-35
Execution:
Tag: @file-validation
Journey: A user pastes content exceeding the 100,000-character limit into the test case box and expects a paste error indicating the content is too long, with the input box remaining empty.
| Scenario |
Given Context |
When Action |
Then Assertion |
Gherkin Type |
|
Pasting content that exceeds the character limit shows an error and does not load the box
|
Format is set to BDD
|
User pastes 100,001 characters into the test case box
|
A paste error containing 'too long' is shown and the test case box remains empty
|
Boundary
|
Test Name: Pasting valid matching content shows no toast
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-34@SHIFT-35
Execution:
Tag: @file-validation
Journey: A user pastes the contents of a valid BDD file that matches the selected format and expects no toast while the content loads successfully into the input box.
| Scenario |
Given Context |
When Action |
Then Assertion |
Gherkin Type |
|
Pasting valid matching content shows no toast
|
Format is set to BDD
|
User pastes the contents of a valid BDD fixture file into the test case box
|
No toast is displayed and the test case box is populated
|
Positive
|
Test Name: Warning toast dismisses and content remains loaded
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-33
Execution:
Tag: @file-validation
Journey: A user uploads a mismatched file, receives a warning toast, dismisses it, and expects the file content to remain loaded in the input box.
| Scenario |
Given Context |
When Action |
Then Assertion |
Gherkin Type |
|
Warning toast dismisses and content remains loaded
|
Format is set to Robot Framework and a mismatched Playwright file has been uploaded, producing a warning toast
|
User dismisses the warning toast
|
The test case box remains populated after the toast is dismissed
|
Edge Case
|
Test Name: Dropping multiple test case files in single-file mode shows a dismissible warning
Feature: Test case file validation on the Analyze page
Traceability:
@SHIFT-48
Execution:
Tag: @file-validation
Journey: A user drops multiple files onto the test case input while in single-file mode, sees a dismissible warning prompting them to switch to multi-file mode, and can dismiss it to clear the message.
| Scenario |
Given Context |
When Action |
Then Assertion |
Gherkin Type |
|
Dropping multiple test case files in single-file mode shows a dismissible warning
|
Format is set to BDD and the page is in single-file mode
|
User drops multiple files onto the test case input, then clicks the dismiss button on the warning
|
A warning message advising multi-file mode is shown with a dismiss button and an empty test case box; after dismissal the warning is no longer visible
|
Negative
|