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: src/content/5/en/part5d.md
+2-5Lines changed: 2 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,10 +76,7 @@ Let's add an npm script to <i>the backend</i> which starts it in test mode, or s
76
76
}
77
77
```
78
78
79
-
NB! To get Cypress working with WSL2 one might need to do some additional configuring first. These two [links](https://docs.cypress.io/guides/getting-started/installing-cypress#Windows-Subsystem-for-Linux) are great places to [start](https://nickymeuleman.netlify.app/blog/gui-on-wsl2-cypress).
80
-
81
-
./node_modules/.bin/cypress install -------- needed on windows.
**NB** To get Cypress working with WSL2 one might need to do some additional configuring first. These two [links](https://docs.cypress.io/guides/getting-started/installing-cypress#Windows-Subsystem-for-Linux) are great places to [start](https://nickymeuleman.netlify.app/blog/gui-on-wsl2-cypress).
83
80
84
81
When both the backend and frontend are running, we can start Cypress with the command
85
82
@@ -407,7 +404,7 @@ As with unit and integration tests, with E2E tests it is best to empty the datab
407
404
408
405
The solution is to create API endpoints for the backend tests.
409
406
We can empty the database using these endpoints.
410
-
Let's create a new <i>router</i> for the tests
407
+
Let's create a new router for the tests inside the <i>controllers</i> folder, in the <i>testing.js</i> file
0 commit comments