Jump to content

Playwright (software)

Edit links
From Wikipedia, the free encyclopedia
Playwright
Developer(s)Microsoft
Initial releaseJanuary 31, 2020; 4 years ago (2020-01-31)[1]
Stable release
v1.45.1[2] / 3 July 2024; 5 months ago (2024-07-03)
Repositorygithub.com/microsoft/playwright
Written inTypeScript
Operating systemMicrosoft Windows, macOS, Linux
TypeSoftware testing framework for web applications
LicenseApache License 2.0
Websiteplaywright.dev

Playwright is an open-source automation library for browser testing and web scraping[3] developed by Microsoft[4][5] and launched on 31 January 2020, which has since become popular among programmers and web developers.

Playwright 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.[7]

Playwright supports programming languages like 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.

@playwright/test

[edit]

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

History

[edit]

Playwright was announced by Microsoft in January 2020.[11] It was developed to address the need for a unified API for cross-browser testing and to overcome limitations in existing tools like Puppeteer and Selenium. A team of engineers, including those who had previously worked on Puppeteer at Google, contributed to its development.[12] Playwright introduced features like automatic waits, multi-browser support, and network interception, making it a powerful tool for modern web testing. Since its inception, it has been actively maintained and has seen rapid growth and adoption in the web testing community.[13]

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'.[14]

Reception

[edit]

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

References

[edit]
  1. ^ "v0.10.0 release". GitHub. Retrieved 1 June 2022.
  2. ^ Tags · microsoft/playwright · GitHub
  3. ^ Bansal, Mudit; Dar, Muhammad Ameen; Bhat, Moshin Manzoor; Sharma, Tushar; Uniyar, Rishita (2023). "Data Ingestion and Processing using Playwright". TechRxiv.
  4. ^ Yegulalp, Serdar (30 September 2020). "Microsoft's Playwright simplifies tests for Python web apps". InfoWorld. IDG Communications. Retrieved 2 July 2023.
  5. ^ Tung, Liam (1 October 2020). "Microsoft: Playwright for Python language lets you test web apps in all major browsers". ZDNET. Retrieved 2 July 2023.
  6. ^ Judis, Stefan (22 October 2022). "Playwright, a Time-Saving End-to-End Testing Framework". The New Stack. Retrieved 2 July 2023.
  7. ^ Tej, Krishna. "Playwright vs Cypress: A Comparison". BrowserStack. Retrieved 2 July 2023.
  8. ^ "Assertions". Playwright. Microsoft. Retrieved 1 June 2023.
  9. ^ "Library". Playwright. Microsoft. Retrieved 1 June 2023.
  10. ^ "Parallelism and sharding". Playwright. Microsoft. Retrieved 1 June 2023.
  11. ^ Attam, Arjun (30 September 2020). "Announcing Playwright for Python: Reliable end-to-end testing for the web". Microsoft DevBlogs. Microsoft. Retrieved 2 July 2023.
  12. ^ Schiemann, Dylan (30 January 2020). "Microsoft Announces Playwright Alternative to Puppeteer". InfoQ. C4Media. Retrieved 2 July 2023.
  13. ^ Gagan, Luc (1 July 2023). "A Comparative Analysis of Playwright Adoption vs Cypress and Selenium". Rayrun. Retrieved 2 July 2023.
  14. ^ "toHaveTitle assertion". Playwright. Microsoft. Retrieved 1 June 2023.

Further reading

[edit]
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Playwright_(software)&oldid=1262466447"