-
Looking at the **archived** cypress-react-unit-test Github repo it says:
> cypress-react-unit-test has been renamed to @cypress/react and now lives in the main Cypress monorepo
Can you please up…
-
This repo needs to have proper testing put in place to ensure the stability of future releases.
-
first half - same as before
second half - new content
- [x] retry-ability and `should(cb)` in #29
* these are core concepts and we have spent time adding more examples to the kitchensink and…
-
## Summary
Migration of testing to Cypress in a duplicate repository.
## 💬 Description
This issue completes the work for the initial technical setup for the move to Cypress for all forms of tes…
-
With only a few months under my belt with BDD/TDD, I am still learning how to structure these tests to be valid and isolated from each other.
With the Feature/Scenario hierarchy, I am still figurin…
-
### Current Behavior
(React) e2e testing must be setup by hand.
### Desired Behavior
TSDX has an e2e testing solution for React libraries.
### Suggested Solutions
**Add to o…
-
### Current behavior:
I am completely unable to get cypress typings to register for commands created using `Cypress.Commands.add`. I've got a repo that has several e2e projects within it that share…
-
Hello,
I would like my development team to create the selectors to be used by my QA teams while writing their own separated cypress tests.
Is there a way to use the created cypress-selectors in th…
-
### Description
Not clear on how to do code coverage for component testing.
### Why is this needed?
It has been really helpful to me and my organization to be able to use the code coverage report…
-
## What/Why
### What are you proposing?
cypress-testing-library offers bunch of useful Cypress commands which simplified the selector query, and it also encourages developers to write robust, implem…