-
### Current behavior
Component tests hand indefinitely after the message "webpack compiled successfully" is displayed on CI.
They run just fine locally.
One funny fact is that when I was runnin…
-
### Describe the bug
We run Cypress for end-to-end tests. After the test has run, Cypress allows you to look back at snapshots of the DOM at different points for debugging purposes. However, the rele…
-
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
## Ignored or Blocked
These are…
-
### Current behavior
I’ve got a Next app running React 18. In the next.config.js, it has been configured with appDir to support Server Components. When running Cypress and accessing the page, I’m g…
-
### Current behavior
I have a component test that is testing a slate (slatejs.org) editor by simply typing some text. Using the import `cypress/react` the test works fine. Using the import `cypress/r…
-
Lorsque l'on utilise cypress, on a une erreur d'hydratation lorsque l'on utilise react-dsfr. Cela fait planter les tests.
J'ai utilisé le projet de démo pour reproduire, c'est dispo ici : https://g…
-
### Current behavior
My organization recently upgraded from React 17 to React 18 and some tests we had that utilized `cy.clock` and `cy.tick` stopped working in our component tests. It seems `setT…
-
Hi! We've got a fork at https://github.com/replayio-public/cypress-realworld-app that we've been using to generate Cypress runs for use with [Replay.io](https://replay.io).
I'm in the process of ge…
-
## Summary
As the testing process moves from Jest and Puppetter to Cypress, it would be valuable for the consumer to have access to helper utils for Cypress in order to remove 'DRY' code.
## 💬 De…
jd239 updated
3 months ago
-
### Current Behavior
Hi
I have several react apps and corresponding dotnet webapps. They are setup in the same way. I'm passing environment variable NX_PUBLIC_BUILD_NUMBER into every app in the Azur…