Merge pull request #303999 from MicrosoftDocs/main

Auto Publish – main to live - 2025-08-07 22:00 UTC

Author: learn-build-service-prod[bot]

articles/app-testing/playwright-workspaces/concept-determine-optimal-configuration.md

@@ -122,7 +122,7 @@ Experiment with the number of parallel workers to run your tests. Measure the te
 Notice at which point the test completion time no longer reduces as you add more workers. Move to the next step to further optimize your setup.
 
 > [!NOTE]
-> While the service is in preview, the number of [parallel workers per workspace is limited](./resource-limits-quotas-capacity.md) to 50. You can [request an increase of this limit for your workspace](https://aka.ms/mpt/feedback).
+> While the service is in preview, the number of [parallel workers per workspace is limited](./resource-limits-quotas-capacity.md) to 50. You can [request an increase of this limit for your workspace](https://aka.ms/pww/feedback).
 
 ### 6. Scale the client
 

articles/app-testing/playwright-workspaces/how-to-configure-visual-comparisons.md

@@ -53,7 +53,7 @@ import { getServiceConfig, ServiceOS } from '@azure/playwright';
 import { DefaultAzureCredential } from '@azure/identity';
 import config from './playwright.config';
 
-/* Learn more about service configuration at https://aka.ms/mpt/config */
+/* Learn more about service configuration at https://aka.ms/pww/docs/config */
 export default defineConfig(
   config,
   getServiceConfig(config, {

articles/app-testing/playwright-workspaces/how-to-manage-authentication.md

@@ -9,7 +9,7 @@ author: ninallam
 ms.author: ninallam
 ms.date: 08/07/2025
 ms.custom: playwright-workspaces-preview
-zone_pivot_group_filename: playwright-workspaces/zone-pivots-groups.json
+zone_pivot_group_filename: app-testing/playwright-workspaces/zone-pivots-groups.json
 zone_pivot_groups: playwright-workspaces
 ---
 
@@ -55,24 +55,20 @@ To enable authentication using access tokens:
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**
+1. While running the tests, enable access token auth in the `playwright.service.config.ts` file in your setup. 
 
-While running the tests, enable access token auth in the `playwright.service.config.ts` file in your setup. 
-
-```typescript
+    ```typescript
     import { getServiceConfig, ServiceAuth } from '@azure/playwright';
 
-    /* Learn more about service configuration at https://aka.ms/mpt/config */
-    export default defineConfig(config, getServiceConfig( config {
+    /* Learn more about service configuration at https://aka.ms/pww/docs/config */
+    export default defineConfig(config, getServiceConfig( config, {
         serviceAuthType: ServiceAuth.ACCESS_TOKEN
     }));
-```
+    ```
 ::: zone-end
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**
-
 1. While running the tests, enable access token auth in the setup file. 
 
     ```c#
@@ -91,7 +87,7 @@ While running the tests, enable access token auth in the `playwright.service.con
             credential: new DefaultAzureCredential(),
             options: new PlaywrightServiceBrowserClientOptions()
             {
-                
+                ServiceAuth = ServiceAuthType.AccessToken
             }
         )
         {
@@ -109,8 +105,6 @@ While running the tests, enable access token auth in the `playwright.service.con
 
 ## Set up your environment.
 
-### If you're using the **Playwright Test Runner**
-
 To set up your environment, configure the `PLAYWRIGHT_SERVICE_ACCESS_TOKEN` environment variable with the value you obtained in the previous steps. Ensure this environment variable is available in your setup where you are running tests.
 
 We recommend that you use the `dotenv` module to manage your environment. With `dotenv`, you define your environment variables in the `.env` file.
@@ -133,27 +127,23 @@ We recommend that you use the `dotenv` module to manage your environment. With `
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**
-
 To set up your environment, configure the `PLAYWRIGHT_SERVICE_ACCESS_TOKEN` environment variable with the value you obtained in the previous steps. Ensure this environment variable is available in your setup where you are running tests.
 
 ::: zone-end
 
-## Run tests on the service and publish results
+## Run tests on the service
 
-Run Playwright tests against cloud-hosted browsers and publish the results to the service using the configuration you created above.
+Run Playwright tests against cloud-hosted browsers using the configuration you created above.
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**
 ```typescript
 npx playwright test --config=playwright.service.config.ts --workers=20
 ```
 ::: zone-end
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**
 ```bash
 dotnet test -- NUnit.NumberOfTestWorkers=20
 ```

articles/app-testing/playwright-workspaces/how-to-test-local-applications.md

@@ -9,7 +9,7 @@ ms.subservice: playwright-workspaces
 author: ninallam
 ms.author: ninallam
 ms.custom: playwright-workspaces-preview
-zone_pivot_group_filename: playwright-workspaces/zone-pivots-groups.json
+zone_pivot_group_filename: app-testing/playwright-workspaces/zone-pivots-groups.json
 zone_pivot_groups: playwright-workspaces
 ---
 
@@ -30,8 +30,6 @@ You can specify one or multiple networks by using a list of rules. For example,
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**
-
 You can configure the `exposeNetwork` option in `playwright.service.config.ts`. The following example shows how to expose the `localhost` network by using the [`<loopback>`](https://en.wikipedia.org/wiki/Loopback) rule. You can also replace `localhost` with a domain that you want to enable for the service.
 
 ```typescript
@@ -60,8 +58,6 @@ npx playwright test --config=playwright.service.config.ts --workers=20
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**
-
 You can configure the `ExposeNetwork` option in the setup file. The following example shows how to expose the `localhost` network by using the [`<loopback>`](https://en.wikipedia.org/wiki/Loopback) rule. You can also replace `localhost` with a domain that you want to enable for the service. 
 
 ```c#

articles/app-testing/playwright-workspaces/how-to-use-service-config-file.md

@@ -9,25 +9,21 @@ ms.subservice: playwright-workspaces
 author: ninallam
 ms.author: ninallam
 ms.custom: playwright-workspaces-preview
-zone_pivot_group_filename: playwright-workspaces/zone-pivots-groups.json
+zone_pivot_group_filename: app-testing/playwright-workspaces/zone-pivots-groups.json
 zone_pivot_groups: playwright-workspaces
 ---
 
 # Use options available in service package with Playwright Workspaces
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**
-
 This article shows you how to use the options available in the `playwright.service.config.ts` file that was generated for you. 
 If you don't have this file in your code, follow [Quickstart: Run end-to-end tests at scale with Playwright Workspaces](./quickstart-run-end-to-end-tests.md) 
 
 ::: zone-end
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**
-
 This article shows you how to use the options available in the `PlaywrightServiceSetup.cs` file. 
 If you don't have this file in your code, follow [Quickstart: Run end-to-end tests at scale with Playwright Workspaces](./quickstart-run-end-to-end-tests.md) 
 
@@ -42,8 +38,6 @@ If you don't have this file in your code, follow [Quickstart: Run end-to-end tes
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**
-
 Below is a complete example of a `playwright.service.config.ts` file showing all supported configuration options:
 
 ```typescript
@@ -131,8 +125,6 @@ export default defineConfig(
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**
-
 
 Here's version of the setup file with all the available options:
 

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

@@ -9,7 +9,7 @@ ms.subservice: playwright-workspaces
 author: ninallam
 ms.author: ninallam
 ms.custom: playwright-workspaces-preview
-zone_pivot_group_filename: playwright-workspaces/zone-pivots-groups.json
+zone_pivot_group_filename: app-testing/playwright-workspaces/zone-pivots-groups.json
 zone_pivot_groups: playwright-workspaces
 ---
 
@@ -67,8 +67,6 @@ To get the service endpoint URL and store it as a CI workflow secret, perform th
 
 ## Add service configuration file
 
-### If you're using the **Playwright Test Runner**
-
 If you don't have Playwright tests configured to run with the service, add a service configuration file to your repository. In the next step, you then specify this service configuration file on the Playwright CLI.
 
 1. Create a new file `playwright.service.config.ts` alongside the `playwright.config.ts` file.
@@ -99,8 +97,6 @@ Update the `package.json` file in your repository to add details about Playwrigh
 
 ## Install service package
 
-### If you're using the **NUnit Test Runner**
-
 In your project, install Playwright Workspaces package. 
 
 ```PowerShell
@@ -111,7 +107,7 @@ This command updates your project's `csproj` file by adding the service package
 
 ```xml
   <ItemGroup>
-    <PackageReference Include="Azure.Developer.Playwright.NUnit" Version="1.0.0-beta.1" />
+    <PackageReference Include="Azure.Developer.Playwright.NUnit" Version="1.0.0-beta.2" />
   </ItemGroup>
 ```
 
@@ -223,7 +219,6 @@ You can generate an access token from your Playwright workspace and use it in yo
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**
 Update the CI workflow definition to run your Playwright tests with the Playwright CLI. Pass the [service configuration file](#add-service-configuration-file) as an input parameter for the Playwright CLI. You configure your environment by specifying environment variables.
 
 1. Open the CI workflow definition.
@@ -324,8 +319,6 @@ Update the CI workflow definition to run your Playwright tests with the Playwrig
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**
-
 Update the CI workflow definition to run your Playwright tests with the Playwright NUnit CLI. You configure your environment by specifying environment variables.
 
 1. Open the CI workflow definition.

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

@@ -9,7 +9,7 @@ ms.subservice: playwright-workspaces
 author: ninallam
 ms.author: ninallam
 ms.custom: playwright-workspaces-preview
-zone_pivot_group_filename: playwright-workspaces/zone-pivots-groups.json
+zone_pivot_group_filename: app-testing/playwright-workspaces/zone-pivots-groups.json
 zone_pivot_groups: playwright-workspaces
 ---
 
@@ -70,8 +70,6 @@ To get started with running your Playwright tests on cloud browsers, you first n
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**
-
 To use the service, install the Playwright Workspaces package. 
 
 ```npm
@@ -86,8 +84,6 @@ If you already have this file, the package asks you to overwrite it.
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**
-
 To use the service, install the Playwright Workspaces package. 
 
 ```PowerShell
@@ -118,8 +114,6 @@ To get the service endpoint URL, perform the following steps:
 
 ## Set up your environment
 
-### If you're using the **Playwright Test Runner**
-
 To set up your environment, you have to configure the `PLAYWRIGHT_SERVICE_URL` environment variable with the value you obtained in the previous steps.
 
 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 `
 
 ::: zone pivot="nunit-test-runner"
 
-## Set up service configuration 
-
-### If you're using the **NUnit Test Runner**
+## Set up service configuration
 
 Create a file `PlaywrightServiceSetup.cs` in your project with the following content. 
 
@@ -165,7 +157,7 @@ public class PlaywrightServiceNUnitSetup  : PlaywrightServiceBrowserNUnit
 ```
 
 > [!NOTE]
-> Make sure your project uses `Microsoft.Playwright.NUnit` version 1.47 or above.
+> Make sure your project uses `Microsoft.Playwright.NUnit` version 1.50 or above.
 
 ::: zone-end
 ## Set up Authentication
@@ -202,8 +194,6 @@ You can generate an access token from your Playwright workspace and use it in yo
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**
-
 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).
 
 ### Run a single test with the service
@@ -334,8 +324,6 @@ To run your Playwright test suite in Visual Studio Code with Playwright Workspac
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**
-
 Run Playwright tests against browsers managed by the service using the configuration you created above. 
 
 ```bash
@@ -364,13 +352,11 @@ With Playwright Workspaces, you can run with up to 50 parallel workers. Several
 
 ::: zone pivot="playwright-test-runner"
 
-### If you're using the **Playwright Test Runner**
 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.
 ::: zone-end
 
 ::: zone pivot="nunit-test-runner"
 
-### If you're using the **NUnit Test Runner**
 You can specify the number of parallel workers on the Playwright CLI command-line, or configure the `NumberOfTestWorkers` property in the `.runsettings` file.
 ::: zone-end
 

articles/app-testing/playwright-workspaces/resource-limits-quotas-capacity.md

@@ -35,7 +35,7 @@ While the service is in preview, the following limits apply on a per-subscriptio
 
 ## Test code limitations
 
-- The service supports Playwright OSS version 1.47 or higher.
+- The service supports Playwright OSS version 1.50 or higher.
 - The service supports the Playwright test runner and the NUnit test runner only.
 
 ## Supported operating systems and browsers