Skip to content

Commit 61924d3

Browse files
committed
mention correct e2e test command in summaries
1 parent 1e722e5 commit 61924d3

File tree

5 files changed

+7
-7
lines changed

5 files changed

+7
-7
lines changed

exercises/02.authentication/01.solution.basic/README.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,11 +15,11 @@
1515
1. In the test, use the newly created `createUser()` utility, which generates a new user and creates it in the database.
1616
1. Log in by filling the log in form as the user would.
1717
1. Assert that the authentication is successful based on the user profile link being visible on the screen.
18-
1. `npm run test:e2e:run`.
18+
1. `npm run test:e2e`.
1919

2020
---
2121

2222
1. Another test case in the same file focused on displaying an error when authentication fails.
2323
1. Similar steps but _no setup_ so the user doesn't exist.
2424
1. Assert the error message being shown (correct _role_ and text).
25-
1. `npm run test:e2e:run`.
25+
1. `npm run test:e2e`.

exercises/02.authentication/02.solution.2fa/README.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,4 +19,4 @@
1919

2020
---
2121

22-
1. `npm run test:e2e:run`. to confirm.
22+
1. `npm run test:e2e`. to confirm.

exercises/02.authentication/03.solution.passkeys/README.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,9 @@
1010
1. Now, we need to tell Playwright how to handle passkeys. In the test, create the `createWebAuthnClient` function and go step-by-step.
1111
1. Use the created `createWebAuthnClient` function to tell the browser how to react to the passkey input prompt (to use our test passkey).
1212
1. Continue with the login flow. Verify the auth state.
13-
1. `npm run test:e2e:run`.
13+
1. `npm run test:e2e`.
1414

1515
---
1616

1717
1. Add another test case for the error scenario.
18-
1. `npm run test:e2e:run`.
18+
1. `npm run test:e2e`.

exercises/02.authentication/04.solution.protected-logic/README.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@
1414
1. Go to a protected route, e.g. to create a new note.
1515
1. Fill in the new note form and submit it.
1616
1. Verify the new note is visible and has the correct content.
17-
1. `npm run test:e2e:run`.
17+
1. `npm run test:e2e`.
1818

1919
---
2020

exercises/03.guides/02.solution.test-data/README.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,4 +6,4 @@
66
1. Complete the test at `tests/e2e/notes-list.test.ts`. Use the new `createNotes` utility to seed some notes for the tested user as a part of the test setup.
77
1. Visit the page that lists all the user's notes.
88
1. Assert that all the notes are visible. Accessibility!
9-
1. `npm run test:e2e:run`.
9+
1. `npm run test:e2e`.

0 commit comments

Comments
 (0)