V
Vanshvsingh
Microsoft Playwright Testing is a managed service built for running Playwright tests easily at scale. As we aim to improve the developer experience, and through our interactions with users, we recognize the need for simpler, more efficient troubleshooting. Today, we’re excited to introduce a new web-hosted reporting dashboard to help speed up the troubleshooting and make it easier for developers to identify and resolve issues. To further enhance security, we’re also implementing Microsoft Entra ID as the default authentication method, providing a more secure and seamless workflow.
Read on to learn more about what’s now possible with Microsoft Playwright Testing.
As development teams scale and iterate rapidly, maintaining high quality becomes more critical than ever. Slow issue resolution impacts the entire development process. With our new reporting feature, anyone on your team can quickly access detailed test results from a CI/CD run, complete with rich artifacts like logs, screenshots, and traces for efficient troubleshooting.
The reporting feature streamlines your workflow by bringing the tests that needs your attention to your notice. The test run view is filtered by failed and flaky tests so that you can start troubleshooting instantly. You can click through each test to find all the information you need to troubleshoot.
Screen capture of troubleshooting in the Playwright dashboard
All test logs and artifacts, including screenshots, videos, and traces are securely stored in a centralized location. They can be accessed through a unified dashboard with configurable permissions.
The Trace Viewer is a powerful tool that is hosted directly in the dashboard. It allows you to visually step through your test execution, or use the timeline to hover over steps and reveal the page state before and after each action. Detailed logs, DOM snapshot, network activity, errors, and console output are available at each test step for precise troubleshooting.
Screenshot of trace viewer hosted in the Playwright dashboard
Test results in the dashboard captures essential CI pipeline details such as commit information, author, and branch, with one click access to the CI pipeline that ran the tests. This enables you to easily investigate code changes that are related to the test result.
For GitHub Actions users, summarized reports are displayed directly in the job summary section, providing a clear overview of test results and direct links to the Playwright dashboard for in-depth analysis.
Screenshot of GitHub Actions job summary
We are also excited to add Microsoft Entra ID support to achieve a more secure default authentication method for Playwright Testing service. Access tokens, though convenient, pose inherent risks such as potential leaks, frequent rotations, and accidental exposure in code. Microsoft Entra ID mitigates these risks by securely authenticating clients with Azure when running tests on cloud-hosted browsers and publishing test reports and artifacts, streamlining workflows and simplifying access control.
Although we recommend using Microsoft Entra ID authentication, access token authentication will still be supported, ensuring flexibility for existing setups and easing the transition to this more secure approach.
Getting started is easy—simply install the service package by running this command:
This will provide you with a configuration file required to and publish test results. You don’t need to modify your test code. Use the newly created Playwright service configuration file to run the tests. The package also facilitates authentication using Microsoft Entra ID and is compatible with Playwright version 1.47 and above.
Next, you can explore our flexible consumption-based pricing where you pay only for what you use
Your feedback is invaluable to us. Please share your feedback and help us shape the future of Microsoft Playwright Testing.
Continue reading...
Read on to learn more about what’s now possible with Microsoft Playwright Testing.
Reporting Dashboard
As development teams scale and iterate rapidly, maintaining high quality becomes more critical than ever. Slow issue resolution impacts the entire development process. With our new reporting feature, anyone on your team can quickly access detailed test results from a CI/CD run, complete with rich artifacts like logs, screenshots, and traces for efficient troubleshooting.
The reporting feature streamlines your workflow by bringing the tests that needs your attention to your notice. The test run view is filtered by failed and flaky tests so that you can start troubleshooting instantly. You can click through each test to find all the information you need to troubleshoot.
Screen capture of troubleshooting in the Playwright dashboard
Troubleshoot easily using rich artifacts
All test logs and artifacts, including screenshots, videos, and traces are securely stored in a centralized location. They can be accessed through a unified dashboard with configurable permissions.
The Trace Viewer is a powerful tool that is hosted directly in the dashboard. It allows you to visually step through your test execution, or use the timeline to hover over steps and reveal the page state before and after each action. Detailed logs, DOM snapshot, network activity, errors, and console output are available at each test step for precise troubleshooting.
Screenshot of trace viewer hosted in the Playwright dashboard
Seamless integration with CI pipelines
Test results in the dashboard captures essential CI pipeline details such as commit information, author, and branch, with one click access to the CI pipeline that ran the tests. This enables you to easily investigate code changes that are related to the test result.
For GitHub Actions users, summarized reports are displayed directly in the job summary section, providing a clear overview of test results and direct links to the Playwright dashboard for in-depth analysis.
Screenshot of GitHub Actions job summary
Securely authenticate using Microsoft Entra ID
We are also excited to add Microsoft Entra ID support to achieve a more secure default authentication method for Playwright Testing service. Access tokens, though convenient, pose inherent risks such as potential leaks, frequent rotations, and accidental exposure in code. Microsoft Entra ID mitigates these risks by securely authenticating clients with Azure when running tests on cloud-hosted browsers and publishing test reports and artifacts, streamlining workflows and simplifying access control.
Although we recommend using Microsoft Entra ID authentication, access token authentication will still be supported, ensuring flexibility for existing setups and easing the transition to this more secure approach.
Get started with Playwright Testing service
Getting started is easy—simply install the service package by running this command:
npm init /microsoft-playwright-testingThis will provide you with a configuration file required to and publish test results. You don’t need to modify your test code. Use the newly created Playwright service configuration file to run the tests. The package also facilitates authentication using Microsoft Entra ID and is compatible with Playwright version 1.47 and above.
Next, you can explore our flexible consumption-based pricing where you pay only for what you use
Share your feedback
Your feedback is invaluable to us. Please share your feedback and help us shape the future of Microsoft Playwright Testing.
Learn more about the Microsoft Playwright Testing service
- Learn more about using the Playwright Testing service for your web application testing.
- Explore the features and benefits that Microsoft Playwright Testing offers.
- Learn about our flexible pricing.
- Use the pricing calculator to determine your costs based on your business needs.
Continue reading...