Let's Create a Playwright Template Project

Lines worth screenshotting.

• A standard UI automation framework has three layers — test scripts, page objects, and support utilities — while Gherkin/SpecFlow frameworks add a fourth feature-file layer that costs more to build and maintain.
• Automation engineers who use GitHub for version control are, by that fact alone, developers — not a separate lesser category from software engineers.
• The single most common request in an automation interview is a basic login-and-logout flow, which makes it worth pre-building before you ever walk into the room.
• Password fields should never display their plaintext value during an automated test recording — treat any tool that shows the password as typed as a disqualifying red flag.
• Test suites should be organized into smoke (roughly the first 10% of the app), sanity (the next 20%), and regression (everything else that has passed before).
• Tests marked work-in-progress but still left running will read as real failures and cause false alarms — exclude WIP tests from the run entirely instead of ignoring their red X.
• Ballooning cross-browser coverage from Chrome-only to Chrome, Edge, Safari, and three versions back roughly triples the maintenance burden without a proportional gain in real coverage.
• Hard-coded sleep waits are the first thing an experienced automation architect looks for, and rejects, when reviewing someone else's test project.
• A CI/CD pipeline that automatically reruns a failed test once, and lets a pass on the second try stand, is correctly treating a transient glitch as noise rather than a real bug.
• Monkey-patching a library's built-in fill() and click() methods lets every test action self-document with a console log line, with zero changes required in any file that calls them.
• Custom data attributes like data-qa are worth requesting from developers because, unlike CSS classes or auto-generated IDs, teams tend to treat them as a stable contract they won't casually break.
• Don't automate a date-picker widget by clicking through its calendar UI — if the input field accepts typed text, just type the date directly instead.
• A transient on-screen "Toast" pop-up that vanishes in about five seconds can still be validated after the fact by capturing it into an array the moment it appears.