You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -415,6 +415,32 @@ make test
415
415
This command runs tests and checks that coverage threshold requirements are satisfied for both backend and frontend.
416
416
**Please note your PR won't be merged if it fails the code tests checks.**
417
417
418
+
### Setting Up e2e Testing Environment
419
+
420
+
Follow these steps to setup your e2e testing environment:
421
+
422
+
1. Make sure you have `gzip` installed on your machine.
423
+
424
+
2. Run the e2e backend instance with the following command:
425
+
426
+
```bash
427
+
make run-backend-e2e
428
+
```
429
+
430
+
3. Load the data into the e2e db with the following command (in another terminal session):
431
+
432
+
```bash
433
+
make load-data-e2e
434
+
```
435
+
436
+
4. Now, you can stop the backend instance, and run the frontend e2e tests with the following command:
437
+
438
+
```bash
439
+
make test-frontend-e2e
440
+
```
441
+
442
+
**Please note that you only need to do these steps once.**
443
+
418
444
### Test Coverage
419
445
420
446
- There is a **minimum test coverage requirement**for the **backend** code -- see [pyproject.toml](https://github.com/OWASP/Nest/blob/main/backend/pyproject.toml).
0 commit comments