-
### Current behavior
An error message is output when closing the Cypress Runner using the runner menu although there was no test running.
> We detected that the electron tab running Cypress test…
-
Right now, the macOS/Safari combination has not been vetted in the regression tests. Support for Safari (WebKit) is deemed "experimental" by Cypress, so there may be issues to be checked as some tests…
kmdvs updated
2 months ago
-
If I execute something like this:
cypress-parallel -s cy:run -t 5 -d ".\cypress\e2e\regression\**"
The tests that are inside the regression subfolders are not being split correctly between the 5 t…
-
1. Userflow using the sliders -> getting cat message
2. Userflow using the sliders -> get dog
-
Currently there are no tests, some options:
- React Testing Library via Jest or Vitetest
- Cypress for e2e
- Playwright (most interesting solution https://github.com/vercel/next.js/blob/canary/packag…
-
Currently Cypress tests take 30 mins to run. To reduce this time we can parallelise the tests to see if this reduces the overall test time.
-
Currently, the sidebar is not visible on the docs however, there is no test in place to detect a failure like this currently. Therefore, adding Cypress to cover e2e tests to minimise regressions makin…
-
A test failed on a tracked branch
```
CypressError: `cy.task('createEndpointHost')` timed out after waiting `600000ms`.
https://on.cypress.io/api/task
Because this error occurred during a `before a…
-
### Current behavior
I've set up Cypress and tried to integrate it into our pipeline. So far, I got Cypress up and running and a few working tests that run successfully using the GUI.
Now when t…
-