-
Notifications
You must be signed in to change notification settings - Fork 4
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
Selenium tests failing locally due to React error overlay #1824
Comments
@grzanka Yes. If there are any errors, even unrelated, the tests will fail because the overlay blocks Selenium from interacting with the application. |
What do you think about investigating why the overlay appears at all and modify the code to fix it (to make overlay gone), not the tests ? |
@grzanka Yes, there probably shouldn't be errors to begin with and the source should be investigated. However, the failing tests cause issues when working on unrelated things. I made this change in order to run tests locally for the mui bump, I wouldn't be able to finish it otherwise. |
Can you invest 15 min on checking what can be the source of the error ? Is it some asynchronous code executed without a catch ? |
@grzanka Sure, I'll take a look at it. |
Does this problem appear with vite as well ? |
It should disappear with vite. |
note: I've managed to narrow the error down to this commit: 16153ed |
When testing locally, if a React error overlay is present, Selenium attempts to interact with elements behind the overlay, causing exceptions and failing assertions due to unexpected screen content.
Example (In FlukaConverter.test.ts):
This can be solved by disabling the overlay for testing purposes.
The text was updated successfully, but these errors were encountered: