The Tools Landscape

Selenium, Playwright, Cypress, Appium, Postman, JMeter, k6 — QA job postings read like a parade of product names, and beginners assume each is a separate world requiring separate months. They aren't. A handful of categories explains the whole parade, and category-thinking is the durable skill: tools churn yearly; the categories have been stable for a decade. This page is the map — and the questions that make any tool comparison meaningful.

Kitchen appliances make the point. Blender, food processor, stand mixer: overlapping jobs, different fits. A cook who understands the categories — what chops, what mixes, what kneads — orients in any kitchen in minutes. A cook who memorized one blender's buttons is lost at the next counter.

UI Automation Drivers

The category from last topic: programs that operate a browser — find, act, assert, at scale. Three names dominate postings, one honest line each. Selenium — the veteran standard: oldest, works with every browser and every programming language, enormous installed base; showing its age in ergonomics but far from dead, whatever the internet says. Playwright — the fast-rising modern one (Microsoft-backed): built-in waiting strategies that kill whole families of flakiness, strong tooling, the current momentum leader. Cypress — the developer favorite: runs inside the browser, pleasant to write, historically JavaScript-centric. What actually differs: speed, language support, built-in conveniences, who tends to adopt them. What doesn't: find/act/assert, locators, assertions, waits — the concepts you already own transfer whole. Learn any one and the second costs a week, not a year.

The Rest of the Map

Five boxes, and the parade is sorted: every tool in every QA posting you'll ever read lives in one of them (plus the trackers you met in Chapter 6). When a new name appears — and one appears yearly — your first question is now "which box?", and the box tells you what concepts apply before you've read a single tutorial.

How to Read a Tool Comparison

Sooner than you'd expect, someone will ask your opinion on tools — and the professional answer is a set of questions, not a brand loyalty. Does it fit our platform? A web-only product doesn't need Appium; a product with heavy Safari traffic cares about true cross-browser support. Does it fit our team's language? Automation code lives next to product code; a team writing in one language wants tests in the same one — this shortlists faster than any benchmark. Is it maintained and does the hiring pool know it? A tool nobody maintains or knows is a liability with good documentation. And the meta-question: "which tool is best?" is the wrong question — "which fits this team?" is the right one. While we're near the folklore: "Selenium is dead" gets declared annually and remains false — enormous suites run on it, jobs require it, and the concepts are identical anyway. Momentum and fit are real considerations; internet funerals are not.

Nadia's Question

And so it happens at Fernway: Nadia asks you — the person who now knows the manual suite best — to recommend a UI automation tool for the pyramid plan. You don't know the tools deeply. You know the category questions, and they're enough. Fernway is a web product (all three drivers fit — Appium excluded, no native app automation needed yet). Omar's team writes in one primary language (that shortlists to the drivers with first-class support for it). Hiring matters for the eventual second QA (that weights the popular ones). Your one-page comparison — three tools, four fit-questions, a recommendation with reasons — is category-thinking on display, and it's a genuinely junior-appropriate task: nobody expects you to have written a thousand tests in each; they expect you to ask the right questions in a defensible order. Which, as of this page, you do.