Selenium tests failing locally due to React error overlay

[tudde]

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):

NoSuchElementError: no such element: Unable to locate element: {"method":"xpath","selector":"//button[contains(text(),'Generate from Editor')]"}

This can be solved by disabling the overlay for testing purposes.

[grzanka]

Do you mean such overlay, as displayed in gitpod enviroment ?

[tudde]

@grzanka Yes. If there are any errors, even unrelated, the tests will fail because the overlay blocks Selenium from interacting with the application.

[grzanka]

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 ?
It seems like source of some kind of errors/problems.

[tudde]

@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.
This change might not be that necessary, I can close this issue if you think so.

[grzanka]

Can you invest 15 min on checking what can be the source of the error ?

Is it some asynchronous code executed without a catch ?

[tudde]

@grzanka Sure, I'll take a look at it.

[grzanka]

Does this problem appear with vite as well ?

#1696

[NiEkOKsU]

It should disappear with vite.

[tudde]

note: I've managed to narrow the error down to this commit: 16153ed
I wasn't able to find out what's causing it just yet