Playwright (software)

The topic of this article may not meet Wikitia's general notability guideline. Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted.
Find sources: "Playwright" software – news · newspapers · books · scholar · JSTOR (Learn how and when to remove this template message)

|

PlaywrightInitial release| January 31, 2020; 5 years ago (2020-01-31)[1]

|

Written in| TypeScript
Operating system| Microsoft Windows, macOS, Linux
Type| Software testing framework for web applications
License| Apache License 2.0

Playwright.[2] is a popular open-source automation library for browser testing and web scraping[3], developed by Microsoft[4][5]. It provides the ability to automate browser tasks in Chromium, Firefox, and WebKit[6], with a single API. This allows developers to create reliable end-to-end tests that are capable of running in non-headless mode, as well as in headless mode for automation. Playwright has been compared to Cypress (software)[7].

Playwright has support for multiple programming languages, including JavaScript, Python, C#, and Java, though its main API was originally written in Node.js. It supports all modern web features, including network interception and multiple browser contexts, and provides automatic waiting which reduces the flakiness of tests[8]

## Contents

* 1 @playwright/test
* 2 History
* 3 Usage and Examples
* 4 Reception
* 5 References
* 6 External links

## @playwright/test[edit]

@playwright/test is a test runner with Jest (framework)-like assertions[9] that is built on top of the Playwright API. It is developed and maintained by the same team as Playwright. This test runner is tightly integrated with Playwright and is specifically designed for end-to-end testing[10]. It has capabilities like browser-specific tests, parallel test execution[11], rich browser context options, snapshot testing, automatic retries, and many more.

## History[edit]

Playwright was announced by Microsoft in January 2020[12]. It was developed by a team of engineers who had previously worked on similar projects like Puppeteer at Google[13]. Since its inception, Playwright has been actively maintained and has seen rapid growth and adoption in the web testing community[14].

The @playwright/test runner was released later as part of an effort to provide a more comprehensive solution for browser-based testing. Its development was largely based on the need to have a specialized runner that can leverage the full potential of the Playwright API and make end-to-end testing more robust and straightforward.

## Usage and Examples[edit]

Playwright is primarily used for automating browser tasks, which can range from simple page navigation and content scraping to more complex operations like automated form submissions, user interactions, and more. For instance, a simple JavaScript code snippet using Playwright might look like:

const { chromium } = require('playwright');

(async () => {
const browser = await chromium.launch();
const page = await browser.newPage();
await page.goto('https://example.com');
await page.screenshot({ path: 'example.png' });
await browser.close();
})();

In this example, Playwright is used to open a Chromium browser, navigate to 'https://example.com', take a screenshot, and save it as 'example.png'.

@playwright/test further extends these capabilities by providing a test runner that allows developers to write and organize their tests in a more structured and scalable manner. An example test using @playwright/test might look like:

const { test } = require('@playwright/test');

test('basic test', async ({ page }) => {
await page.goto('https://example.com');
await expect(page).toHaveTitle('Example Domain');
});

In this example, a test is written to navigate to 'https://example.com' and check if the title of the page is 'Example Domain'[15].

## Reception[edit]

Both Playwright and @playwright/test have been well received by the developer community. They are praised for their robustness, speed[16] and widely used in the industry, playing an important role in web application testing and development.

## References[edit]

1. ↑ "v0.10.0 release". GitHub.
2. ↑ "Playwright Website".
3. ↑ Bansal, Mudit; DAR, MUHAMMAD AMEEN; BHAT, MOHSIN MANZOOR; SHARMA, TUSHAR; UNIYAL, RISHITA (2023). "Data Ingestion and Processing using Playwright". TechRxiv.
4. ↑ Yegulalp, Serdar (September 30, 2020). "Microsoft's Playwright simplifies tests for Python web apps". InfoWorld.com. IDG Communications. Retrieved July 2, 2023.
5. ↑ Tung, Liam (October 1, 2020). "Microsoft: Playwright for Python language lets you test web apps in all major browsers". zdnet.com. ZDNET. Retrieved July 2, 2023.
6. ↑ Judis, Stefan (October 22, 2022). "Playwright, a Time-Saving End-to-End Testing Framework". thenewstack.io. The New Stack. Retrieved July 2, 2023.
7. ↑ Tej, Krishna. "Playwright vs Cypress: A Comparison". BrowserStack. Retrieved July 2, 2023.
8. ↑ "Why Playwright?". playwright.dev.
9. ↑ "Assertions".
10. ↑ "Library".
11. ↑ "Parallelism and sharding".
12. ↑ Attam, Arjun (30 September 2020). "Announcing Playwright for Python: Reliable end-to-end testing for the web". devblogs.microsoft.com. Microsoft. Retrieved July 2, 2023.
13. ↑ Schiemann, Dylan (January 30, 2020). "Microsoft Announces Playwright Alternative to Puppeteer". InfoQ.com. C4Media. Retrieved July 2, 2023.
14. ↑ Gagan, Luc (July 2023). "A Comparative Analysis of Playwright Adoption vs Cypress and Selenium". Rayrun. Retrieved July 2, 2023.
15. ↑ "toHaveTitle assertion".
16. ↑ Gagan, Luc (28 June 2023). "Comparing Automated Testing Tools: Cypress, Selenium, Playwright, and Puppeteer". ray.run. Rayrun. Retrieved July 2, 2023.

## External links[edit]

Add External links

This article "Playwright (software)" is from Wikipedia. The list of its authors can be seen in its historical. Articles taken from Draft Namespace on Wikipedia could be accessed on Wikipedia's Draft Namespace.