-
**Describe the bug**
Cypress debug does not work with Google chrome (116).
```
Cypress failed to make a connection to the Chrome DevTools Protocol after retrying for 50 seconds.
This usually i…
-
### Issue description or question
Running tests in PhpStorm 2023.3.1 with Wallaby.js App v1.0.86, Core v1.0.1511.
Launching coverage / test explorer -> selecting "FILES" and clicking on file to op…
-
### Current behavior
Setting `watchForFileChanges` to `false` seems to have no effect in component testing (i.e. when starting Cypress with `npx cypress open-ct`).
It *does* work with regular Cy…
-
Spike for the research is 2h.
-
When I run a single test in webstorm I've got an error in output
Did you see this before?
-
As of late last week, Cypress tests are failing with this error, from one commit to the next, which was completely unrelated (an `.md` file). I seem to be getting the same error as @jazanne from [this…
-
Type: Bug
Open Visual Studio Code for Insiders and open Copilot Chat.
VS Code version: Code - Insiders 1.82.0-insider (1606401f5b761397488f53b75130809fba073194, 2023-08-07T05:36:30.820Z)
OS version…
-
### Issue description or question
When running my tests with intellij I get the errors in the console :
![image](https://github.com/wallabyjs/public/assets/2129896/11941ffd-a277-452e-9370-c91053b52…
-
##### **Overview of the issue**
After a newly generated JHipster project is created. Main options: Angular, Gradle, H2, Cypress, Gatling, Cucumber.
Opened up project in IntelliJ. Started proj…
-
### Steps to reproduce
1. Log into Element via SSO
2. Have the session be soft-logged-out
### Outcome
#### What did you expect?
I expect to be able to restore the session via another SSO login.…