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
+24Lines changed: 24 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -415,6 +415,30 @@ 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. Run the e2e backend instance with the following command:
423
+
424
+
```bash
425
+
make run-backend-e2e
426
+
```
427
+
428
+
2. Load the data into the e2e db with the following command (in another terminal session):
429
+
430
+
```bash
431
+
make load-data-e2e
432
+
```
433
+
434
+
3. Now, you can stop the backend instance, and run the frontend e2e tests with the following command:
435
+
436
+
```bash
437
+
make test-frontend-e2e
438
+
```
439
+
440
+
**Please note that you only need to do these steps once.**
441
+
418
442
### Test Coverage
419
443
420
444
- 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