Testing Strategies #8
Replies: 2 comments 5 replies
-
I've added some initial tests in both vitest & cypress (#26, #30) because they were already instrumented in the Indie Stack, and it was a good opportunity for me to try something that's new to me (vitest), as well as to learn more about the GitHub Actions to run everything via CI/CD. However, it would be easy to implement another solution instead! So I'm still totally open to discussing using Jest instead of vitest, and Playwright instead of Cypress. I'd love for others to chime in! |
Beta Was this translation helpful? Give feedback.
-
Calling bankruptcy on all discussions and issues today. Going to start revamping the direction of this project, so stay tuned 🚀 |
Beta Was this translation helpful? Give feedback.
-
How do we want to test the site?
Related is #2, but there are some initial questions and infra we should setup.
@grantnorwood bootstrapped this project with the Indie Stack, which gives us Cypress and Jest out the gate.
Personally, I'm all in on Jest + Testing Library for unit tests and component tests.
As far as Cypress, I think it's fine and the infra is there, so that's cool! However, I'm a little more excited about Playwright these days for end-to-end (e2e) testing.
Curious other's thoughts? Have an idea you'd rather show through code, open a PR!
Beta Was this translation helpful? Give feedback.
All reactions