Skip to content

Commit 7230b9c

Browse files
committed
fixed acrolinx suggestions
1 parent ff6899b commit 7230b9c

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/playwright-testing/quickstart-generate-rich-reports-for-tests.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.custom: playwright-testing-preview
88

99
# Quickstart: Troubleshoot tests with Microsoft Playwright Testing Preview
1010

11-
In this quickstart, you learn how to troubleshoot your Playwright tests easily using reports and artifacts published on Microsoft Playwright Testing Preview. Additionally, this guide demonstrates how to utilize the reporting feature, regardless of whether you are running tests on the cloud-hosted browsers provided by the service.
11+
In this quickstart, you learn how to troubleshoot your Playwright tests easily using reports and artifacts published on Microsoft Playwright Testing Preview. Additionally, this guide demonstrates how to utilize the reporting feature, regardless of whether you're running tests on the cloud-hosted browsers provided by the service.
1212

1313
After you complete this quickstart, you'll have a Microsoft Playwright Testing workspace to view test results and artifacts in the service portal.
1414

@@ -51,7 +51,7 @@ To use the service, install the Microsoft Playwright Testing package.
5151
npm init @azure/microsoft-playwright-testing
5252
```
5353

54-
This generates `playwright.service.config.ts` file which serves to:
54+
This command generates `playwright.service.config.ts` file which serves to:
5555

5656
- Direct and authenticate your Playwright client to the Microsoft Playwright Testing service.
5757
- Adds a reporter to publish test results and artifacts.
@@ -73,7 +73,7 @@ export default defineConfig(
7373
}
7474
);
7575
```
76-
Setting this as `false` ensures that cloud-hosted browsers are not used to run the tests. The tests run on your local machine but the results and artifacts are published on the service.
76+
Setting the value as `false` ensures that cloud-hosted browsers aren't used to run the tests. The tests run on your local machine but the results and artifacts are published on the service.
7777

7878
> [!TIP]
7979
> If you wish to accelerate your test run using cloud-hosted browser, you can set `useCloudHostedBrowsers` as true, This will run your tests on the service managed browsers.
@@ -113,7 +113,7 @@ We recommend that you use the `dotenv` module to manage your environment. With `
113113

114114
## Set up Authentication
115115

116-
To publish test results and artifacts to your Microsoft Playwright Testing workspace, you need to authenticate the Playwright client where you're running the tests with the service. This could be your local dev machine or CI machine.
116+
To publish test results and artifacts to your Microsoft Playwright Testing workspace, you need to authenticate the Playwright client where you're running the tests with the service. The client could be your local dev machine or CI machine.
117117
118118
The service offers two authentication methods: Microsoft Entra ID and Access Tokens.
119119
@@ -141,7 +141,7 @@ You can generate an access token from your Playwright Testing workspace and use
141141
> We strongly recommend using Microsoft Entra ID for authentication to the service. If you are using access tokens, see [How to Manage Access Tokens](./how-to-manage-access-tokens.md)
142142

143143
## Enable artifacts in Playwright configuration
144-
In the `playwright.config.ts` file of your project, make sure you are collecting all the required artifacts.
144+
In the `playwright.config.ts` file of your project, make sure you're collecting all the required artifacts.
145145
```typescript
146146
use: {
147147
trace: 'on-first-retry',

0 commit comments

Comments
 (0)