diff --git a/docs/src/codegen-intro.md b/docs/src/codegen-intro.md index 82d44fe90d..871b03f3cd 100644 --- a/docs/src/codegen-intro.md +++ b/docs/src/codegen-intro.md @@ -1,6 +1,6 @@ --- id: codegen-intro -title: "Test generator" +title: "Generating tests" --- Playwright comes with the ability to generate tests out of the box and is a great way to quickly get started with testing. It will open two windows, a browser window where you interact with the website you wish to test and the Playwright Inspector window where you can record your tests, copy the tests, clear your tests as well as change the language of your tests. diff --git a/docs/src/running-tests-csharp.md b/docs/src/running-tests-csharp.md index 290cb9b343..3b954ec3dc 100644 --- a/docs/src/running-tests-csharp.md +++ b/docs/src/running-tests-csharp.md @@ -1,6 +1,6 @@ --- id: running-tests -title: "Running tests" +title: "Running and debugging tests" --- You can run a single test, a set of tests or all tests. Tests can be run on different browsers. By default tests are run in a headless manner meaning no browser window will be opened while running the tests and results will be seen in the terminal. If you prefer you can run your tests in headed mode by using the `headless` test run parameter. diff --git a/docs/src/running-tests-java.md b/docs/src/running-tests-java.md index bb3fa96a4a..b1b8a5c81c 100644 --- a/docs/src/running-tests-java.md +++ b/docs/src/running-tests-java.md @@ -1,6 +1,6 @@ --- id: running-tests -title: "Running tests" +title: "Running and debugging tests" --- Playwright tests can be run in a variety of ways. We recommend hooking it up to your favorite test runner, e.g. [JUnit](./test-runners.md) since it gives you the ability to run tests in parallel, run single test, etc. diff --git a/docs/src/running-tests-js.md b/docs/src/running-tests-js.md index f4cb7e7fc0..2ae7591469 100644 --- a/docs/src/running-tests-js.md +++ b/docs/src/running-tests-js.md @@ -1,10 +1,10 @@ --- id: running-tests -title: "Running tests" +title: "Running and debugging tests" --- ## Introduction -With Playwright you can run a single test, a set of tests or all tests. Tests can be run on one browser or multiple browsers by using the `--project` flag. Tests are run in parallel by default and are run in a headless manner meaning no browser window will be opened while running the tests and results will be seen in the terminal. However you can run tests in headed mode by using the `--headed` CLI argument or you can run your tests in UI mode, by using the `--ui` flag, and see a full trace of your tests complete with watch mode, time travel debugging and more. +With Playwright you can run a single test, a set of tests or all tests. Tests can be run on one browser or multiple browsers by using the `--project` flag. Tests are run in parallel by default and are run in a headless manner meaning no browser window will be opened while running the tests and results will be seen in the terminal. However you can run tests in headed mode by using the `--headed` CLI argument or you can run your tests in [UI mode](./test-ui-mode.md), by using the `--ui` flag, and see a full trace of your tests complete with watch mode, time travel debugging and more. **You will learn** @@ -12,13 +12,8 @@ With Playwright you can run a single test, a set of tests or all tests. Tests ca - [How to debug tests](/running-tests.md#debugging-tests) - [How to open the HTML test reporter](/running-tests.md#test-reports) -## VS Code extension - -Tests can be run right from VS Code using the [VS Code extension](https://marketplace.visualstudio.com/items?itemName=ms-playwright.playwright). Once installed you can simply click the green triangle next to the test you want to run or run all tests from the testing sidebar. Check out our [Getting Started with VS Code](./getting-started-vscode.md#running-tests) guide for more details. - -![Playwright VS Code extension](https://github.com/microsoft/playwright/assets/13063165/47726e70-683b-4bd5-94de-7d03dd45c30f) - -## Command line +## Running tests +### Command line You can run your tests with the `playwright test` command. This will run your tests on all browsers as configured in the `playwright.config` file. Tests run in headless mode by default meaning no browser window will be opened while running the tests and results will be seen in the terminal. @@ -88,6 +83,12 @@ To run a test with a specific title use the `-g` flag followed by the title of t npx playwright test -g "add a todo item" ``` +### Run tests in VS Code + +Tests can be run right from VS Code using the [VS Code extension](https://marketplace.visualstudio.com/items?itemName=ms-playwright.playwright). Once installed you can simply click the green triangle next to the test you want to run or run all tests from the testing sidebar. Check out our [Getting Started with VS Code](./getting-started-vscode.md#running-tests) guide for more details. + +![Playwright VS Code extension](https://github.com/microsoft/playwright/assets/13063165/47726e70-683b-4bd5-94de-7d03dd45c30f) + ## Debugging tests Since Playwright runs in Node.js, you can debug it with your debugger of choice e.g. using `console.log` or inside your IDE or directly in VS Code with the [VS Code Extension](./getting-started-vscode.md). Playwright comes with [UI Mode](./test-ui-mode.md), where you can easily walk through each step of the test, see logs, errors, network requests, inspect the DOM snapshot and more. You can also use the [Playwright Inspector](./debug.md#playwright-inspector) which allows you to step through Playwright API calls, see their debug logs and explore [locators](./locators.md). diff --git a/docs/src/running-tests-python.md b/docs/src/running-tests-python.md index de38ccc290..dca252c960 100644 --- a/docs/src/running-tests-python.md +++ b/docs/src/running-tests-python.md @@ -1,6 +1,6 @@ --- id: running-tests -title: "Running tests" +title: "Running and debugging tests" --- ## Introduction @@ -11,7 +11,9 @@ You can run a single test, a set of tests or all tests. Tests can be run on one - [How to run tests from the command line](/running-tests.md#command-line) - [How to debug tests](/running-tests.md#debugging-tests) -## Command Line +## Running tests + +### Command Line To run your tests use the `pytest` command. This will run your tests on the Chromium browser by default. Tests run in headless mode by default meaning no browser window will be opened while running the tests and results will be seen in the terminal.