updated service config for NUnit

Author: vvs11

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

@@ -4,19 +4,35 @@ description: Learn how to use options available in configuration file with Micro
 ms.topic: how-to
 ms.date: 09/07/2024
 ms.custom: playwright-testing-preview
+zone_pivot_group_filename: playwright-testing/ZonePivotGroups.json
+zone_pivot_groups: microsoft-playwright-testing
 ---
+::: zone pivot="playwright-test-runner"
 # Use options available in configuration file with Microsoft Playwright Testing preview
 
 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 the QuickStart guide, see [Quickstart: Run end-to-end tests at scale with Microsoft Playwright Testing Preview](./quickstart-run-end-to-end-tests.md) 
 
+::: zone-end
+
+::: zone pivot="nunit-test-runner"
+
+# Use options available in configuration file with Microsoft Playwright Testing preview
+
+This article shows you how to use the options available in the `.runsettings` file. 
+If you don't have this file in your code, follow the QuickStart guide, see [Quickstart: Run end-to-end tests at scale with Microsoft Playwright Testing Preview](./quickstart-run-end-to-end-tests.md) 
+
+::: zone-end
+
 > [!IMPORTANT]
 > Microsoft Playwright Testing is currently in preview. For legal terms that apply to Azure features that are in beta, in preview, or otherwise not yet released into general availability, see the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
 ## Prerequisites
 
 * Follow the Quickstart guide and set up a project to run with Microsoft Playwright Testing service. See, [Quickstart: Run end-to-end tests at scale with Microsoft Playwright Testing Preview](./quickstart-run-end-to-end-tests.md) 
 
+::: zone pivot="playwright-test-runner"
+
 Here's version of the `playwright.service.config.ts` file with all the available options:
 
 ```typescript
@@ -136,4 +152,123 @@ export default defineConfig(
         ],
       ]
     ```
+::: zone-end
+
+::: zone pivot="nunit-test-runner"
+
+
+Here's version of the `.runsettings` file with all the available options:
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<RunSettings>
+    <TestRunParameters>
+        <!-- Use this option when you want to authenticate using access tokens. This mode of auth should be enabled for the workspace. -->
+         <Parameter name="ServiceAuthType" value="EntraId" />
+        <!-- Select the operating system where you want to run tests. -->
+        <Parameter name="Os" value="linux" />
+        <!-- Set a unique ID for every test run to distinguish them in the service portal.-->
+        <Parameter name="RunId" value="sample-run-id1" />
+        <!--Select if you want to use cloud-hosted browsers to run your Playwright tests.-->
+        <Parameter name="UseCloudHostedBrowsers" value="true" />
+        <!--Select the authentication method you want to use with Entra-->
+        <Parameter name="AzureTokenCredentialType" value="DefaultAzureCredential" />
+        <!--Enable/disable GitHub summary in GitHub Actions workflow.-->
+        <Parameter name="EnableGitHubSummary" value="false" />
+    </TestRunParameters>
+  <!-- NUnit adapter -->  
+  <NUnit>
+    <!-- Adjust parallel workers, parallel worker would also be bound by number of unit test files -->
+    <NumberOfTestWorkers>10</NumberOfTestWorkers>
+  </NUnit>
+  <!-- General run configuration -->
+  <RunConfiguration>
+    <EnvironmentVariables>
+      <!-- For debugging selectors, it's recommend to set the following environment variable -->
+      <DEBUG>pw:api</DEBUG>
+    </EnvironmentVariables>
+  </RunConfiguration>
+  <!-- Playwright -->  
+  <Playwright>
+    <BrowserName>chromium</BrowserName>
+    <!--Set the timeout for your tests.-->
+    <ExpectTimeout>5000</ExpectTimeout>
+    <LaunchOptions>
+      <Headless>false</Headless>
+      <!--Channel>msedge</Channel-->
+    </LaunchOptions>
+  </Playwright>
+    <LoggerRunSettings>
+        <Loggers>
+            <!--microsoft playwright testing service logger for reporting -->
+            <Logger friendlyName="microsoft-playwright-testing" enabled="True" />
+            <!--could enable any logger additionally -->
+            <Logger friendlyName="trx" enabled="false" />
+        </Loggers>
+    </LoggerRunSettings>
+</RunSettings>
+
+```
+
+## Options in `.runsettings` file
+
+* **`serviceAuthType`**:
+    - **Description**: This setting allows you to choose the authentication method you want to use for your test run. 
+    - **Available Options**:
+        - `ACCESS_TOKEN` to use access tokens. You need to enable authentication using access tokens if you want to use this option, see [manage authentication](./how-to-manage-authentication.md).
+        - `ENTRA_ID` to use Microsoft Entra ID for authentication. It's the default mode. 
+    - **Default Value**: `ENTRA_ID`
+    - **Example**:
+      ```xml
+      <Parameter name="ServiceAuthType" value="EntraId" />
+      ```
+
+
+* **`os`**:
+    - **Description**: This setting allows you to choose the operating system where the browsers running Playwright tests are hosted.
+    - **Available Options**:
+        - "windows" for Windows OS.
+        - "linux" for Linux OS.
+    - **Default Value**: "linux"
+    - **Example**:
+      ```xml
+      <Parameter name="Os" value="linux" />
+      ```
+
+* **`runId`**:
+    - **Description**: This setting allows you to set a unique ID for every test run to distinguish them in the service portal.
+    - **Example**:
+      ```xml
+      <Parameter name="RunId" value="sample-run-id1" />
+      ```
 
+* **`AzureTokenCredentialType`**:
+    - **Description**: This setting allows you to select the authentication method you want to use with Microsoft Entra ID.
+    - **Example**:
+      ```xml
+      <Parameter name="AzureTokenCredentialType" value="DefaultAzureCredential" />
+      ```
+
+* **`useCloudHostedBrowsers`**
+    - **Description**: This setting allows you to choose whether to use cloud-hosted browsers or the browsers on your client machine to run your Playwright tests. If you disable this option, your tests run on the browsers of your client machine instead of cloud-hosted browsers, and you don't incur any charges.
+    - **Default Value**: true
+    - **Example**:
+      ```xml
+      <Parameter name="UseCloudHostedBrowsers" value="true" />
+      ```   
+
+* **`reporter`**
+    - **Description**: You can publish your test results and artifacts to the service using `microsoft-playwright-testing` logger. You can disable reporting by removing this from your `.runsettings`
+    - **Default Value**: true
+    - **Example**:
+      ```xml
+     <Logger friendlyName="microsoft-playwright-testing" enabled="True" />
+      ```
+* **`enableGitHubSummary`**:
+    - **Description**: This setting allows you to configure the Microsoft Playwright Testing service reporter. You can choose whether to include the test run summary in the GitHub summary when running in GitHub Actions.
+    - **Default Value**: true
+    - **Example**:
+    ```xml
+      <Parameter name="EnableGitHubSummary" value="false" />
+    ```
+::: zone-end

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

@@ -309,7 +309,7 @@ Run Playwright tests against browsers managed by the service and see the results
 ```bash
 dotnet test --logger "microsoft-playwright-testing"
 ```
-After the test run completes, you can view the test status in the terminal.. 
+After the test run completes, you can view the test status in the terminal.
 
 ```output
 Starting test execution, please wait...