-
Notifications
You must be signed in to change notification settings - Fork 9
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
Examples: add tests #72
Comments
Adding remove some agility to examples. As when a hacker play with them they may need to update/remove the tests. Could do very basic tests:
Best to ship first with the new react components. In terms of testing usefulness for examples. Hopefully, any functional issue with Waku would be detected in the js-waku test suite. |
In waku-org/js-waku#1542 this was partially addressed. I think at this point this issue can be closed. @fryorcraken re-open if disagree |
non-regression tests are needed to ensure that the show case, deployed on
master
branch updates, still works.Also, remove
WakuMock
once the tests are in place.The text was updated successfully, but these errors were encountered: