Skip to content

Commit 0dd64a6

Browse files
authored
Update quickstart-run-end-to-end-tests.md
1 parent 21865e5 commit 0dd64a6

File tree

1 file changed

+2
-16
lines changed

1 file changed

+2
-16
lines changed

articles/app-testing/playwright-workspaces/quickstart-run-end-to-end-tests.md

Lines changed: 2 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.subservice: playwright-workspaces
99
author: ninallam
1010
ms.author: ninallam
1111
ms.custom: playwright-workspaces-preview
12-
zone_pivot_group_filename: playwright-workspaces/zone-pivots-groups.json
12+
zone_pivot_group_filename: app-testing/playwright-workspaces/zone-pivots-groups.json
1313
zone_pivot_groups: playwright-workspaces
1414
---
1515

@@ -70,8 +70,6 @@ To get started with running your Playwright tests on cloud browsers, you first n
7070

7171
::: zone pivot="playwright-test-runner"
7272

73-
### If you're using the **Playwright Test Runner**
74-
7573
To use the service, install the Playwright Workspaces package.
7674

7775
```npm
@@ -86,8 +84,6 @@ If you already have this file, the package asks you to overwrite it.
8684

8785
::: zone pivot="nunit-test-runner"
8886

89-
### If you're using the **NUnit Test Runner**
90-
9187
To use the service, install the Playwright Workspaces package.
9288

9389
```PowerShell
@@ -118,8 +114,6 @@ To get the service endpoint URL, perform the following steps:
118114

119115
## Set up your environment
120116

121-
### If you're using the **Playwright Test Runner**
122-
123117
To set up your environment, you have to configure the `PLAYWRIGHT_SERVICE_URL` environment variable with the value you obtained in the previous steps.
124118

125119
We recommend that you use the `dotenv` module to manage your environment. With `dotenv`, you define your environment variables in the `.env` file.
@@ -142,9 +136,7 @@ We recommend that you use the `dotenv` module to manage your environment. With `
142136

143137
::: zone pivot="nunit-test-runner"
144138

145-
## Set up service configuration
146-
147-
### If you're using the **NUnit Test Runner**
139+
## Set up service configuration
148140

149141
Create a file `PlaywrightServiceSetup.cs` in your project with the following content.
150142

@@ -202,8 +194,6 @@ You can generate an access token from your Playwright workspace and use it in yo
202194

203195
::: zone pivot="playwright-test-runner"
204196

205-
### If you're using the **Playwright Test Runner**
206-
207197
You've now prepared the configuration for running your Playwright tests in the cloud with Playwright Workspaces. You can either use the Playwright CLI to run your tests, or use the [Playwright Test Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=ms-playwright.playwright).
208198
209199
### Run a single test with the service
@@ -334,8 +324,6 @@ To run your Playwright test suite in Visual Studio Code with Playwright Workspac
334324
335325
::: zone pivot="nunit-test-runner"
336326
337-
### If you're using the **NUnit Test Runner**
338-
339327
Run Playwright tests against browsers managed by the service using the configuration you created above.
340328
341329
```bash
@@ -364,13 +352,11 @@ With Playwright Workspaces, you can run with up to 50 parallel workers. Several
364352

365353
::: zone pivot="playwright-test-runner"
366354

367-
### If you're using the **Playwright Test Runner**
368355
You can specify the number of parallel workers on the Playwright CLI command-line, or configure the `workers` property in the Playwright service configuration file.
369356
::: zone-end
370357

371358
::: zone pivot="nunit-test-runner"
372359

373-
### If you're using the **NUnit Test Runner**
374360
You can specify the number of parallel workers on the Playwright CLI command-line, or configure the `NumberOfTestWorkers` property in the `.runsettings` file.
375361
::: zone-end
376362

0 commit comments

Comments
 (0)