Playwright as a tool consists of two main parts.
Part 1: Playwright Library: This is the automation of a browser using the Page Object Model (POM). It provides a uniform API to run against the 3 main browser engines, automating tasks like navigating, clicking, filling in form data, and validating content on a web page. Classes include APIRequest, APIResponse, and BrowserContext. The worker process runs the API calls sequentially. Unified library API calls are sent to the browser context, which runs unaware of the calling context.
 |
| Top link runs in Node.js and makes API library calls, there is no timing between the Node.js (Controller) and the browser instance (running Chromium instance) |
Part 2: Test Runner: This part runs the Playwright tests.
Playwright Series
Playwright Post 1 - Overview of E2E testing using Playwright (this post)
Playwright Post 2 - Continuously Test/Monitor Canvas apps and website with MFA enabled
Playwright Post 3 - Add App Insights logging inside your Playwright tests
Playwright Post 4 - 6 Min walkthru of Playwright testing with Azure Monitor
Playwright Post 5 - Understanding how playwright works (this post)
Playwright Post 6 - Unattended testing when secured with MFA
Other Posts
Upgrading two C# Blazor web applications and verifying using Playwright - super fast
Mendix - Part 2 - Diving deeper (E2E automation testing of Mendix using Playwright)
Low-code testing with playwright walkthru
Continiously Monitor Apps using Playwright with TS
Testing Canvasa apps with Playwright using C# (rather use TS, it's better)
