-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: update README for @cypress/react (add commands to run tests) #22477
docs: update README for @cypress/react (add commands to run tests) #22477
Conversation
Thanks for taking the time to open a PR!
|
fb903f7
to
44b0c31
Compare
As of Cypress 10, adding React and Component Testing should be a lot easier. You might want to try setting up a React project with Cypress 10, if you haven't already - it's almost completely automated. Thanks for the PR either way 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will look to get this one merged - need to trigger a CI run for this.
Thank you! I'm glad that I can contribute to such a great repo. |
Test summaryRun details
View run in Cypress Dashboard ➡️ Flakiness
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
User facing changelog
n/a
Additional details
When I tried to add Cypress component tests into my React app, this README file helped me a lot.
But I got stuck for a while after installing and initialization. I didn't know how to run the component tests. It cost some time to figure it out.
So I added these commands in the README, hope this can save some beginners some time.
How has the user experience changed?
n/a
PR Tasks
cypress-documentation
?type definitions
?