use the test command for e2e tests

kettanaito · kettanaito · commit 398ff64ac25c · 2025-07-17T12:15:45.000+02:00
diff --git a/exercises/01.basics/01.problem.install-and-configure/README.mdx b/exercises/01.basics/01.problem.install-and-configure/README.mdx
@@ -18,7 +18,7 @@ npx playwright install --with-deps chromium
 
 🐨 Next, create `playwright.config.ts` file at the root of your project. This is Playwright's configuration file. You will use it to set up Playwright in the way that makes sense for your project.
 
-🐨 In `package.json`, create a new script called `test:e2e`. You will use this script to run your end-to-end tests at the end of this exercise. Use the `playwright test` command as the value for that script.
+🐨 In `package.json`, create a new script called `test`. You will use this script to run your end-to-end tests at the end of this exercise. Use the `npx playwright test` command as the value for that script.
 
 🐨 Create a directory called `tests`. In that directory, create a new test file called `epicweb.test.ts`.
 
@@ -45,4 +45,4 @@ To do that, your test would have to perform a series of steps:
 
 3. Assert that the heading element is visible on the page via `await expect(element).toBeVisible()`.
 
-🐨 Finally, run this test via `npm run test:e2e` in the terminal. You should see it passing.
+🐨 Finally, run this test via `npm test` in the terminal. You should see it passing.
diff --git a/exercises/01.basics/02.problem.running-the-app/README.mdx b/exercises/01.basics/02.problem.running-the-app/README.mdx
@@ -8,4 +8,4 @@
 
 🐨 Now that `webServer` is configured, it's time to write some tests! Let's start from testing the homepage of the app. I've already got a test file prepared for you at <InlineFile file="./tests/e2e/homepage.test.ts">`tests/e2e/homepage.test.ts`</InlineFile>. Open that file and write a test case there.
 
-Once you're done, make sure that the added test is passing by running the `npm run test:e2e:run` command in your terminal.
+Once you're done, make sure that the added test is passing by running the `npm test` command in your terminal.
diff --git a/exercises/01.basics/02.problem.running-the-app/package.json b/exercises/01.basics/02.problem.running-the-app/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/01.basics/02.solution.running-the-app/package.json b/exercises/01.basics/02.solution.running-the-app/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/02.test-setup/01.problem.custom-fixtures/README.mdx b/exercises/02.test-setup/01.problem.custom-fixtures/README.mdx
@@ -8,4 +8,4 @@
 
 🐨 Once the fixture is ready, refactor the <InlineFile file="./tests/e2e/homepage.test.ts">`tests/e2e/homepage.test.ts`</InlineFile> test suite to use the newly created `navigate()` fixture.
 
-And, of course, verify that the tests are passing in the end by running `npm run test:e2e:run`. Good luck!
+And, of course, verify that the tests are passing in the end by running `npm test`. Good luck!
diff --git a/exercises/02.test-setup/01.problem.custom-fixtures/package.json b/exercises/02.test-setup/01.problem.custom-fixtures/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/02.test-setup/01.solution.custom-fixtures/package.json b/exercises/02.test-setup/01.solution.custom-fixtures/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/02.test-setup/03.problem.authentication/README.mdx b/exercises/02.test-setup/03.problem.authentication/README.mdx
@@ -14,4 +14,4 @@ npm i playwright-persona -D
 
 🐨 Once you've defined the `user` persona and created the `authenticate()` fixture, continue to the <InlineFile file="./tests/e2e/notes-create.test.ts">`tests/e2e/notes-create.test.ts`</InlineFile> test suite and finish the test case here.
 
-Verify your solution by running the tests (`npm run test:e2e:dev`). The tests must pass!
+Verify your solution by running the tests (`npm test`). The tests must pass!
diff --git a/exercises/02.test-setup/03.problem.authentication/package.json b/exercises/02.test-setup/03.problem.authentication/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/02.test-setup/03.solution.authentication/package.json b/exercises/02.test-setup/03.solution.authentication/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/02.test-setup/04.problem.api-mocking/README.mdx b/exercises/02.test-setup/04.problem.api-mocking/README.mdx
@@ -14,4 +14,4 @@ npm i msw @msw/playwright --save-dev
 
 🐨 Once you've got the `network` fixture ready, it's time to put it into action. In the <InlineFile file="./tests/e2e/notes-created.test.ts">`tests/e2e/notes-created.test.ts`</InlineFile> test file, complete the test case for a new note creation. In this one, you'd have to intercept an HTTP request to the Google Places API that happens on the client to suggest a list of places for the note's "Location" field. As always, 🐨 Kody and his instructions will guide you to success.
 
-By the end of it all, the tests (`npm run test:e2e:dev`) must pass!
+By the end of it all, the tests (`nnpm test`) must pass!
diff --git a/exercises/02.test-setup/04.problem.api-mocking/package.json b/exercises/02.test-setup/04.problem.api-mocking/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/02.test-setup/04.solution.api-mocking/package.json b/exercises/02.test-setup/04.solution.api-mocking/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/02.test-setup/05.problem.test-data/README.mdx b/exercises/02.test-setup/05.problem.test-data/README.mdx
@@ -10,4 +10,4 @@
 
 🐨 Next, head to the test case in <InlineFile file="./tests/e2e/notes-list.test.ts">`tests/e2e/utils.ts`</InlineFile> and complete it, using the newly-created `createNotes` utility.
 
-🐨 Finally, run the `npm run test:e2e:dev` command to make sure that the test is passing. Trigger the test run multiple times to verify that your test setup cleans up after itself and the test results are idempotent.
+🐨 Finally, run the `npm test` command to make sure that the test is passing. Trigger the test run multiple times to verify that your test setup cleans up after itself and the test results are idempotent.
diff --git a/exercises/02.test-setup/05.problem.test-data/package.json b/exercises/02.test-setup/05.problem.test-data/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/02.test-setup/05.solution.test-data/package.json b/exercises/02.test-setup/05.solution.test-data/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/03.guides/01.problem.recording-interactions/package.json b/exercises/03.guides/01.problem.recording-interactions/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/03.guides/01.solution.recording-interactions/package.json b/exercises/03.guides/01.solution.recording-interactions/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/03.guides/02.problem.test-annotations/package.json b/exercises/03.guides/02.problem.test-annotations/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/03.guides/02.solution.test-annotations/README.mdx b/exercises/03.guides/02.solution.test-annotations/README.mdx
@@ -11,8 +11,8 @@ Things you can do with tags:
 1. Run a subset of tests:
 
 ```sh
-npm run test:e2e -- --grep=@user
-npm run test:e2e -- --grep=@user|@profile
+npm test -- --grep=@user
+npm test -- --grep=@user|@profile
 ```
 
 2. You can also filter and run subset of tests from the UI mode (the "Filter" input at the top left).
diff --git a/exercises/03.guides/02.solution.test-annotations/package.json b/exercises/03.guides/02.solution.test-annotations/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/03.guides/03.problem.blocking-unneeded-requests/README.mdx b/exercises/03.guides/03.problem.blocking-unneeded-requests/README.mdx
@@ -18,4 +18,10 @@ Let's block this kind of requests in Playwright!
 
 🐨 Go to the <InlineFile name="./tests/test-extend.ts">`tests/test-extend.ts`</InlineFile> file and follow the instructions to intercept the problematic request and handle its response.
 
-🐨 Once you do, run the tests via the `npm run test:e2e:dev` command. Inspect the "Network" tab in Playwright's UI mode that find the request that you have intercepted. It should have an empty response.
+🐨 Finally, it would be great to verify your solution and make sure that the request in question indeed receives a mocked response during the test. To do that, run your tests in a UI mode:
+
+```sh
+npm test -- --ui
+```
+
+In the UI mode window, open the "Network" tab and find the request that you have intercepted (`GET /stonks.js`). You should see it having a mocked response!
diff --git a/exercises/03.guides/03.problem.blocking-unneeded-requests/package.json b/exercises/03.guides/03.problem.blocking-unneeded-requests/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/03.guides/03.solution.blocking-unneeded-requests/package.json b/exercises/03.guides/03.solution.blocking-unneeded-requests/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/04.debugging/01.solution.ui-mode/package.json b/exercises/04.debugging/01.solution.ui-mode/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/04.debugging/02.problem.trace-viewer/README.mdx b/exercises/04.debugging/02.problem.trace-viewer/README.mdx
@@ -14,6 +14,6 @@ npx playwright show-trace ./trace.zip
 
 Inspect what the trace view gives you, including the timeline, test actions, the DOM, console, and network to see what hints at the problem.
 
-🐨 A/B your findings with the local run of the test (`npm run test:e2e:dev`) to find the culprit.
+🐨 A/B your findings with the local run of the test (`npm test`) to find the culprit.
 
 🐨 Once you've found the root cause of the issue, outline how you would fix it. We will discuss the approach together in the solution to this exercise.
diff --git a/exercises/04.debugging/02.problem.trace-viewer/package.json b/exercises/04.debugging/02.problem.trace-viewer/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/04.debugging/02.solution.trace-viewer/README.mdx b/exercises/04.debugging/02.solution.trace-viewer/README.mdx
@@ -11,7 +11,7 @@ You can generate a trace of your local test run by setting the `--trace` CLI opt
 ```sh
 npx playwright test --trace on
 # or
-npm run test:e2e -- --trace on
+npm test -- --trace on
 ```
 
 ## Related materials
diff --git a/exercises/04.debugging/02.solution.trace-viewer/package.json b/exercises/04.debugging/02.solution.trace-viewer/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/04.debugging/03.problem.live-debugging/package.json b/exercises/04.debugging/03.problem.live-debugging/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",
diff --git a/exercises/04.debugging/03.solution.live-debugging/package.json b/exercises/04.debugging/03.solution.live-debugging/package.json
@@ -18,7 +18,7 @@
     "setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",
     "start": "cross-env NODE_ENV=production node .",
     "start:mocks": "cross-env NODE_ENV=production MOCKS=true tsx .",
-    "test": "vitest",
+    "test": "npx playwright test",
     "coverage": "vitest run --coverage",
     "test:e2e": "npm run test:e2e:dev --silent",
     "test:e2e:dev": "npx playwright test --ui",

Original file line number	Diff line number	Diff line change
`@@ -8,4 +8,4 @@`
`8`	`8`
`9`	`9`	🐨 Now that `webServer` is configured, it's time to write some tests! Let's start from testing the homepage of the app. I've already got a test file prepared for you at <InlineFile file="./tests/e2e/homepage.test.ts">`tests/e2e/homepage.test.ts`</InlineFile>. Open that file and write a test case there.
`10`	`10`
`11`		-Once you're done, make sure that the added test is passing by running the `npm run test:e2e:run` command in your terminal.
	`11`	+Once you're done, make sure that the added test is passing by running the `npm test` command in your terminal.
Original file line number	Diff line number	Diff line change
`@@ -8,4 +8,4 @@`
`8`	`8`
`9`	`9`	🐨 Once the fixture is ready, refactor the <InlineFile file="./tests/e2e/homepage.test.ts">`tests/e2e/homepage.test.ts`</InlineFile> test suite to use the newly created `navigate()` fixture.
`10`	`10`
`11`		-And, of course, verify that the tests are passing in the end by running `npm run test:e2e:run`. Good luck!
	`11`	+And, of course, verify that the tests are passing in the end by running `npm test`. Good luck!
Original file line number	Diff line number	Diff line change
`@@ -14,4 +14,4 @@ npm i playwright-persona -D`
`14`	`14`
`15`	`15`	🐨 Once you've defined the `user` persona and created the `authenticate()` fixture, continue to the <InlineFile file="./tests/e2e/notes-create.test.ts">`tests/e2e/notes-create.test.ts`</InlineFile> test suite and finish the test case here.
`16`	`16`
`17`		-Verify your solution by running the tests (`npm run test:e2e:dev`). The tests must pass!
	`17`	+Verify your solution by running the tests (`npm test`). The tests must pass!