first attempt at e2e tests (#131)

* first attempt at e2e tests remove unused imports remove old comments move __mocks__ and document the reason for it 2e2 test improve e2e test bootstrap e2e: email validation e2e: Get users controller routes Patch e2e testing docs * first attempt at e2e tests remove unused imports remove old comments move __mocks__ and document the reason for it 2e2 test improve e2e test bootstrap e2e: email validation e2e: Get users controller routes Patch e2e testing docs * remove old stuff * remove old code and use .env files for e2e_db * mispellings * one .env * docks & solve conflict * address review * fix import & stubs * include e2e tests in checks
Nonprofit-Exchange-Hub · Mar 5, 2022 · fc08972 · fc08972
1 parent 342b3ed
commit fc08972
Show file tree

Hide file tree

Showing 13 changed files with 22,761 additions and 22,419 deletions.
diff --git a/README.md b/README.md
@@ -28,6 +28,8 @@
     DATABASE_PASSWORD=your_password
     DATABASE_DB=test_db
     BCRYPT_WORK_FACTOR=10   
+    # e2e only used when running e2e tests
+    E2E_DATABASE_DB=e2e_db
 ```
 6. In that `.env` file we'll now customize some of those values
     * If you are using the non-dockerized version of postgres, change the `DATABASE_PORT` value to `5432`

diff --git a/server/DEVELOPMENT.md b/server/DEVELOPMENT.md
@@ -0,0 +1,11 @@
+# Server Development
+
+## Unit Testing
+
+Not making the most use of unit testing at the moment due to the amount of mocking it requires - which may be constantly changing while we build the MVP
+
+## e2e (Integration Testing)
+
+We are invensting more time in e2e testing on the server side.
+
+The general strategy is to test the server api endpoints as the front end would use it, so ideally we would have e2e tests for each endpoint. See more details: [e2e testing](test/E2ETESTING.md)