Update documentation

diff --git a/.eslintignore b/.eslintignore
index 4234ddf723d7c011729a2e36c4c603b0204274d6..4aadab1763b091bfb911420685294222787df2c0 100644 (file)
--- a/.eslintignore
+++ b/.eslintignore
@@ -1,3 +1,4 @@
 assets
+build
 dist
 .gitignore

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index bf67cc2cc51ad4add97c0f005f83a1f68185bd13..4da23c2af893ab21a390332cad2c6ced58b44bb8 100644 (file)
--- 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)

diff --git a/README.md b/README.md
index e78b591668d24695a893161315fe03c15ab553c5..e8b6201152eb7b3c0ce676e8a7f4a09d6fae0bf4 100644 (file)
--- a/README.md
+++ b/README.md
@@ -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