-
Notifications
You must be signed in to change notification settings - Fork 392
make the failing tests on e2e actually pass #2486
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR aims to make failing end‐to‐end tests pass by clearly indicating command failures through updated workflow scripts. Key changes include injecting evalScript commands and runFlow blocks into multiple YAML test files and updating config file paths in the test runner script.
- Added explicit evalScript and runFlow commands to simulate failure and recovery in test flows.
- Modified configuration paths in the test runner (e2e/run_tests) to reflect updated file structure.
Reviewed Changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.
Show a summary per file
File | Description |
---|---|
e2e/workspaces/demo_app/fail_visible_extended.yaml | Inserts a runFlow block with pre/post evalScript commands. |
e2e/workspaces/demo_app/fail_visible.yaml | Similar changes using assertVisible command within runFlow. |
e2e/workspaces/demo_app/fail_not_found.yaml | Uses tapOn command with runFlow alterations to simulate failure. |
e2e/workspaces/demo_app/fail_launchApp_nonDefault.yaml | Runs launchApp with specific non-default app id via runFlow. |
e2e/workspaces/demo_app/fail_launchApp.yaml | Updates the launchApp command and evalScript commands in runFlow. |
e2e/workspaces/demo_app/fail_fast.yaml | Adds assertTrue based flow handling with a note on unreachable code. |
e2e/run_tests | Adjusts config file paths for both passing and failing test runs. |
Co-authored-by: Dan Caseley <[email protected]>
Co-authored-by: Dan Caseley <[email protected]>
Co-authored-by: Dan Caseley <[email protected]>
Co-authored-by: Dan Caseley <[email protected]>
Co-authored-by: Dan Caseley <[email protected]>
Co-authored-by: Dan Caseley <[email protected]>
(because we want them to pass by showing the actual command failed)