Playwright testing
Playwright is the browser automation library from Microsoft that drives Chromium, Firefox and WebKit through one API, waits for elements to be ready before acting on them, and records a trace of a failed test.
Open the topicA hub answers the subject first, lists the searches it serves, and points to the guide, the comparison, the tool or the product page for where you are: learning, doing, choosing or proving.
Playwright is the browser automation library from Microsoft that drives Chromium, Firefox and WebKit through one API, waits for elements to be ready before acting on them, and records a trace of a failed test.
Open the topicSelenium is the W3C WebDriver standard and the libraries built on it, the longest-lived way to automate a browser and still the one most enterprise suites are written in.
Open the topicAPI testing checks a service through its interface rather than its screens: the status code, the shape of the response, the values that matter, the time it took and the headers that protect it.
Open the topicA test suite is only as useful as its red builds are believable.
Open the topicAccessibility testing checks that people who use a screen reader, a keyboard alone, magnification or reduced motion can complete a journey.
Open the topicWeb application security testing probes a running application the way an attacker would, through its pages and APIs, and reports what it found.
Open the topicPerformance testing asks how a system behaves under load: how long a request takes at the 95th and 99th percentile, where it breaks, and what fails first.
Open the topicRegression testing re-runs the checks that already passed to prove a change did not break them.
Open the topicTesting in CI/CD means a change cannot reach production without the checks running against it: unit and API tests on every push, a browser smoke test on every deploy, the fuller regression suite and security scans where they fit the budget.
Open the topicAI testing means two different things, and a page that does not say which is selling something.
Open the topicTest data is the part of a test that is hardest to keep honest.
Open the topicCross-browser testing runs the same journey in more than one engine because the engines differ: in default fonts and scrollbars, in which inputs they render natively, in how they treat a download, and in what their automation layer reports.
Open the topicVisual testing compares what a page looks like against what it looked like before, and reports what moved.
Open the topicRecord one flow and get four kinds of evidence back. Judge the results yourself.