Skip to content

Commit 4e5617f

Browse files
authored
Merge pull request #253294 from ntrogh/mpt-overview-diagram
[Microsoft Playwright Testing] Update overview page
2 parents eb80251 + 203f846 commit 4e5617f

File tree

2 files changed

+38
-12
lines changed

2 files changed

+38
-12
lines changed
Loading

articles/playwright-testing/overview-what-is-microsoft-playwright-testing.md

Lines changed: 38 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -10,41 +10,67 @@ ms.custom: playwright-testing-preview
1010

1111
Microsoft Playwright Testing Preview is a fully managed service for end-to-end testing built on top of Playwright. With Playwright, you can automate end-to-end tests to ensure your web applications work the way you expect it to, across different web browsers and operating systems. The service abstracts the complexity and infrastructure for running Playwright tests with high parallelization.
1212

13-
Run your Playwright test suite in the cloud, without changes to your test code or modifications to your tooling setup. Use the Playwright Test Visual Studio Code extension for a rich editor experience, or use the Playwright CLI to add automation within your continuous integration (CI) workflow.
13+
Run your Playwright test suite in the cloud, without changes to your test code or modifications to your tooling setup. Use the [Playwright Test Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=ms-playwright.playwright) for a rich editor experience, or use the Playwright CLI to add automation within your continuous integration (CI) workflow.
1414

1515
Get started with [Quickstart: run your Playwright tests at scale with Microsoft Playwright Testing](./quickstart-run-end-to-end-tests.md).
1616

17-
To learn more about how Playwright works and how to write end-to-end tests, visit the [Getting started documentation](https://playwright.dev/docs/intro) on the Playwright website.
17+
To learn more about how to create end-to-end tests with the Playwright framework, visit the [Getting started documentation](https://playwright.dev/docs/intro) on the Playwright website.
1818

1919
> [!IMPORTANT]
2020
> 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/).
2121
2222
## Accelerate tests with parallel remote browsers
2323

24-
As your application becomes more complex, your test suite increases in size. The time to complete your test suite also grows accordingly.
24+
As your application becomes more complex, your test suite increases in size. The time to complete your test suite also grows accordingly. Use parallel remote browsers to shorten the overall test suite completion time.
2525

26-
Microsoft Playwright Testing enables you to distribute your tests across many parallel remote browsers, hosted on cloud infrastructure. By using cloud-hosted browsers, you can scale your test beyond the processing power of your developer workstation, local infrastructure, or continuous integration (CI) agent machines. This parallelization helps you shorten the overall test suite completion time.
26+
- Distribute your tests across many parallel browsers, hosted on cloud infrastructure.
2727

28-
Microsoft Playwright Testing helps you to [optimize the regional latency](./how-to-optimize-regional-latency.md) between the client machine and the cloud-hosted browsers by creating the hosted browsers in the Azure region that's closest to your client machine. Alternately, you can choose to run your tests on browsers in the region that's linked to your Microsoft Playwright Testing workspace.
28+
- Scale your tests beyond the processing power of your developer workstation, local infrastructure, or CI agent machines.
2929

30-
## Test across multiple operating systems and browsers
30+
- Consistent regional performance by running your tests on browsers in an Azure region that's closest to your client machine.
3131

32-
Application complexity isn’t the only factor in increasing test suite size. Modern web apps need to work flawlessly across numerous browsers, operating systems, and devices. Testing across all these configurations increases the amount of time it takes to run your test suite.
32+
Learn more about how you can [configure for optimal performance](./concept-determine-optimal-configuration.md).
3333

34-
With Microsoft Playwright Testing, you can run these tests simultaneously across all modern browsers on Windows, Linux, and mobile emulation of Google Chrome for Android and Mobile Safari. Microsoft Playwright Testing supports all [browsers supported by Playwright](https://playwright.dev/docs/release-notes).
34+
## Test consistently across multiple operating systems and browsers
3535

36-
## Test web applications regardless of their location
36+
Modern web apps need to work flawlessly across numerous browsers, operating systems, and devices.
3737

38-
You can use Microsoft Playwright Testing for testing both publicly and privately accessible applications, without having to allow inbound connections on your firewall. During the development phase, you can also use Microsoft Playwright Testing to run tests against a localhost development server.
38+
- Run tests simultaneously across all modern browsers on Windows, Linux, and mobile emulation of Google Chrome for Android and Mobile Safari.
39+
40+
- Using service-managed browsers ensures consistent and reliable results for both functional and visual regression testing, whether tests are run from your team's developer workstations or CI pipeline.
41+
42+
- Microsoft Playwright Testing supports all [browsers supported by Playwright](https://playwright.dev/docs/release-notes).
43+
44+
## Endpoint testing
45+
46+
Use cloud-hosted remote browsers to test web applications regardless of where they're hosted, without having to allow inbound connections on your firewall.
47+
48+
- Test publicly and privately hosted applications.
49+
50+
- During the development phase, [run tests against a localhost development server](./how-to-test-local-applications.md).
51+
52+
## Playwright support
53+
54+
Microsoft Playwright Testing is built on top of the Playwright framework.
55+
56+
- Support for multiple versions of Playwright with each new Playwright release.
57+
58+
- Integrate your existing Playwright test suite without changing your test code.
59+
60+
- Use the [Playwright Test Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=ms-playwright.playwright) for a rich editor experience.
61+
62+
- Continuous end-to-end testing by using the Playwright CLI to [integrate with continuous integration (CI) tools](./quickstart-automate-end-to-end-testing.md).
3963

4064
## How it works
4165

4266
Microsoft Playwright Testing instantiates cloud-hosted browsers across different operating systems. Playwright runs on the client machine and interacts with Microsoft Playwright Testing to run your Playwright tests on the hosted browsers. The client machine can be your developer workstation or a CI agent machine if you run your tests as part of your CI workflow. The Playwright test code remains on the client machine during the test run.
4367

44-
To run existing tests with Microsoft Playwright Testing requires no changes to your test code. Add a service configuration file to your test project, and specify your workspace settings, such as the access token and the service endpoint.
68+
:::image type="content" source="./media/overview-what-is-microsoft-playwright-testing/playwright-testing-architecture-overview.png" alt-text="Diagram that shows an architecture overview of Microsoft Playwright Testing." lightbox="./media/overview-what-is-microsoft-playwright-testing/playwright-testing-architecture-overview.png":::
4569

4670
After a test run completes, Playwright sends the test run metadata to the service. The test results, trace files, and other test run files are available on the client machine.
4771

72+
To run existing tests with Microsoft Playwright Testing requires no changes to your test code. Add a service configuration file to your test project, and specify your workspace settings, such as the access token and the service endpoint.
73+
4874
Learn more about how to [determine the optimal configuration for optimizing test suite completion](./concept-determine-optimal-configuration.md).
4975

5076
## In-region data residency & data at rest
@@ -56,4 +82,4 @@ Microsoft Playwright Testing automatically encrypts all data stored in your work
5682
## Next step
5783

5884
> [!div class="nextstepaction"]
59-
> [Run Playwright tests at scale](quickstart-run-end-to-end-tests.md)
85+
> [Quickstart: Run Playwright tests at scale](quickstart-run-end-to-end-tests.md)

0 commit comments

Comments
 (0)