Skip to content

Commit 2a58740

Browse files
committed
fix errors
1 parent 2078ab6 commit 2a58740

File tree

3 files changed

+11
-13
lines changed

3 files changed

+11
-13
lines changed

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

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -68,19 +68,20 @@ To enable authentication using access tokens:
6868
```xml
6969
<TestRunParameters>
7070
<!-- Use this option when you want to authenticate using access tokens. This mode of auth should be enabled for the workspace. -->
71-
<Parameter name="ServiceAuthType" value="EntraId" />
71+
<Parameter name="ServiceAuthType" value="AccessToken" />
7272
</TestRunParameters>
7373
```
7474
::: zone-end
7575

7676
1. Create access token
7777

78-
Follow the steps to [create an access token](./how-to-manage-access-tokens.md#generate-a-workspace-access-token)
78+
Follow the steps to [create an access token](./how-to-manage-access-tokens.md#generate-a-workspace-access-token). Copy the value of the access token generated.
7979

8080

8181
1. Set up your environment
8282

83-
To set up your environment, you have to configure the `PLAYWRIGHT_SERVICE_ACCESS_TOKEN` environment variable with the value you obtained in the previous steps.
83+
To set up your environment, you have to configure the `PLAYWRIGHT_SERVICE_ACCESS_TOKEN` environment variable with the value you obtained in the previous steps. Make sure this environment variable is available in your setup where you are running tests.
84+
8485
::: zone pivot="playwright-test-runner"
8586
We recommend that you use the `dotenv` module to manage your environment. With `dotenv`, you define your environment variables in the `.env` file.
8687

@@ -100,9 +101,6 @@ To enable authentication using access tokens:
100101

101102
::: zone-end
102103

103-
::: zone pivot="nunit-test-runner"
104-
Make sure this environment variable is available in your setup where you are running tests.
105-
::: zone-end
106104
## Run tests on the service and publish results
107105

108106
Run Playwright tests against cloud-hosted browsers and publish the results to the service using the configuration you created above.

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -215,9 +215,9 @@ Here's version of the `.runsettings` file with all the available options:
215215
* **`serviceAuthType`**:
216216
- **Description**: This setting allows you to choose the authentication method you want to use for your test run.
217217
- **Available Options**:
218-
- `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).
219-
- `ENTRA_ID` to use Microsoft Entra ID for authentication. It's the default mode.
220-
- **Default Value**: `ENTRA_ID`
218+
- `AccessToken` 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).
219+
- `EntraId` to use Microsoft Entra ID for authentication. It's the default mode.
220+
- **Default Value**: `EntraId`
221221
- **Example**:
222222
```xml
223223
<Parameter name="ServiceAuthType" value="EntraId" />
@@ -235,7 +235,7 @@ Here's version of the `.runsettings` file with all the available options:
235235
<Parameter name="Os" value="linux" />
236236
```
237237

238-
* **`runId`**:
238+
* **`RunId`**:
239239
- **Description**: This setting allows you to set a unique ID for every test run to distinguish them in the service portal. Using the same runId for multiple test runs results in error. If you don't set it, the service package will generate a unique ID every time you trigger a test run.
240240
- **Example**:
241241
```xml
@@ -249,7 +249,7 @@ Here's version of the `.runsettings` file with all the available options:
249249
<Parameter name="AzureTokenCredentialType" value="DefaultAzureCredential" />
250250
```
251251

252-
* **`useCloudHostedBrowsers`**
252+
* **`UseCloudHostedBrowsers`**
253253
- **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.
254254
- **Default Value**: true
255255
- **Example**:
@@ -264,7 +264,7 @@ Here's version of the `.runsettings` file with all the available options:
264264
```xml
265265
<Logger friendlyName="microsoft-playwright-testing" enabled="True" />
266266
```
267-
* **`enableGitHubSummary`**:
267+
* **`EnableGitHubSummary`**:
268268
- **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.
269269
- **Default Value**: true
270270
- **Example**:

articles/playwright-testing/how-to-use-service-features.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -118,7 +118,7 @@ export default defineConfig(
118118
119119
```
120120

121-
* **`useCloudHostedBrowsers`**
121+
* **`UseCloudHostedBrowsers`**
122122
- **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.
123123
- **Default Value**: true
124124
- **Example**:

0 commit comments

Comments
 (0)