Microsoft just lately introduced the general public preview of Microsoft Playwright Testing, a brand new service for operating Playwright assessments at scale by way of Azure.
Playwright is a fast-growing, open-source framework that permits dependable end-to-end testing and automation for contemporary net apps. It makes use of a single API to regulate Chromium, Firefox, WebKit, and Opera browsers. Microsoft will provide the framework by way of a managed service, claiming that customers can “run Playwright assessments with a lot greater parallelization throughout totally different working system-browser mixtures concurrently.”
With the @playwright/check runner, assessments run in impartial, parallel employee processes, with every course of beginning its personal browser. Furthermore, growing the variety of parallel employees can cut back the time it takes to finish the complete check suite. Nonetheless, when operating assessments domestically or in a steady integration (CI) pipeline, there’s a limitation to the variety of central processing unit (CPU) cores on an area machine or CI agent machine.
Mandy Whaleya accomplice director of product, Azure Dev Instruments at Microsoft, writes:
By utilizing Microsoft Playwright Testing service, you’ll be able to improve the variety of employees at cloud-scale to a lot greater numbers. The employee processes orchestrated by @playwright/check proceed to run domestically, however the browser cases, that are resource-intensive, now run within the cloud.
With Microsoft Playwright Testing, builders can use the scalable parallelism offered by the service to run net app assessments concurrently throughout all trendy rendering engines corresponding to Chromium, WebKit, and Firefox on Home windows and Linux and cellular emulation of Google Chrome for Android and Cellular Safari. As well as, the service-managed browsers guarantee constant and dependable outcomes for useful and visible regression testing, whether or not assessments run from a CI pipeline or improvement machine.
Overview Microsoft Playwright Testing service from CI pipelines and code editors (Supply: Developer instruments weblog submit)
To successfully use Microsoft Playwright Testing, builders should create a workspace in Azure, subsequently, generate an entry token and a region-specific service endpoint. With the token and endpoint, builders can enter these of their setting variables and leverage these settings of their challenge, i.e., playwright.service.config.ts they should create alongside the playwright.config.ts file. Lastly, they’ll run assessments utilizing the Playwright CLI or Visible Studio Code.
Operating Playwright assessments on distant browsers in a workspace, the CLI command can appear like this:
npx playwright check --config=playwright.service.config.ts --workers=20
Alternate options for Playwright Testing can be found, corresponding to the favored Selenium, Cypress.io, and Puppeteer. These will be leveraged within the cloud for scale; as an illustration, Cypress.io gives the chance to make use of Cypress Cloud, and Puppeteer will be run in Cloud Capabilities.
With Playwright Testing out there as a managed service in Azure, David Osolkowskia software program engineer at Vyne Dental, tweeted on X:
Is that this a precursor to Playwright disappearing in its present kind and solely being out there/maintained as a service? I’m bored with the enshittification of software program instruments, however possibly it’s time to hop again on the treadmill and search for another…
Amanda Silvera CVP of the Developer Division at Microsoft, replied in a tweet:
No. Playwright will proceed to be an OSS FX unto itself.
Lastly, extra particulars on Microsoft Playwright Testing can be found on the documentation touchdown web page and GitHub repo, and pricing will be discovered on the pricing web page.
