-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
add tests #7
Comments
hey @smeijer have you any preference about folder structure, or configuration? |
I usually place my tests next to the files they cover. Like:
Test config files (if required), I usually place in But I'm open to suggestions. |
I usually prefer to separate the things to be clearer but this is a good solution too :) |
I don't mind making Unit Tests, I would like to try out Cypress using your project, if you are cool with that of course. |
I think that the project need also E2E testing so I think could be ok. |
@JacobMGEvans, go for it 👍 I believe it's great to have those tests. |
Awesome! On it. |
Closing this one. The test setup was added by #12, and the individual tests will be an ongoing issue. |
A testing-playground.com without tests... I don't think that should be a thing, but at this moment it is.
We should fix that, and use jest & testing-library to do it.
The text was updated successfully, but these errors were encountered: