diff options
| -rw-r--r-- | .eslintignore | 1 | ||||
| -rw-r--r-- | CONTRIBUTING.md | 1 | ||||
| -rw-r--r-- | README.md | 5 |
3 files changed, 5 insertions, 2 deletions
diff --git a/.eslintignore b/.eslintignore index 4234ddf..4aadab1 100644 --- a/.eslintignore +++ b/.eslintignore @@ -1,3 +1,4 @@ assets +build dist .gitignore diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index bf67cc2..4da23c2 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -24,6 +24,7 @@ Some ideas so far include: Above All: Be nice, always. - Ensure the style checkers show no warnings or errors +- Make sure all tetsts are passing - Don't break the CI - Make the PRs according to [Git Flow][gitflow]: (features go to develop, hotfixes go to master) @@ -16,13 +16,14 @@ that's running before starting. ## Testing -You can run tests with `npm test`. The tests use `testing-library` and -`jest`. +You can run tests with `npm test`. The tests use `testing-library`, `pact`, +and `jest`. Here's some short guidelines: - Every component that receives props or changes state should be tested. - Test expected outcomes, not implementation details. - Avoid mocking unless it's an external call + - Stores that interact with the API should be tested using pact [node]: https://nodejs.org/en/ [forum-server]: https://gitlab.com/rbdr/forum-server |