Topic
16 articles tagged “automation”.
Should you use page objects, fixtures, or plain hooks in Playwright? We wrote the same three Sauce Demo tests all three ways, ran them, and measured the differences: how much code each needs, how many places a locator lives, where a failure points when a locator breaks, and what a beforeEach does to a test that doesn't need it.
playwright · automation · tutorial
8 MIN
A hands-on introduction to accessibility testing. Scan a page with axe, read a violation properly, see the same bug in the accessibility tree and in your locators, then find out why a keyboard pass misses it entirely. Includes an exercise with an answer key.
accessibility · playwright · automation
9 MIN
A pairwise model of the Sauce Demo checkout, 31 generated cases run as a data-driven Playwright test on Chromium, Firefox, and WebKit, and a run of every account, product, and form combination to check what those cases found and what they could have missed.
test cases · playwright · automation
16 MIN
A file-by-file look at what Playwright's planner, generator, and healer agents are allowed to do, plus the review rules we recommend before letting a healer edit your tests.
playwright · ai · automation
6 MIN
Real defects from this site's own codebase: what the symptom was, which check caught it, the root cause, the fix, and the regression test we added.
case study · playwright · accessibility
6 MIN
Updated
A hands-on introduction to API testing: explore an API with curl, write a Postman collection and run it with Newman, then write the same checks in Playwright. Uses a public practice API whose real responses include a few surprises.
api testing · postman · rest
9 MIN
Updated
A working Cucumber project from feature file to green build: Gherkin scenarios and a Scenario Outline, step definitions with hooks, a JUnit Platform suite runner, and the dependency mismatch that breaks it if you add JUnit 6.
cucumber · bdd · gherkin
7 MIN
Updated
One test (log in, add a product, check the cart badge) written in Cypress, Playwright, and Selenium against the same public demo shop. How the code differs, how long each run took, what broke during setup, and which framework fits which team.
cypress · playwright · selenium
7 MIN
Updated
A complete, working Selenium WebDriver project: Maven dependencies, a page object, explicit waits, JUnit tests, and a troubleshooting section built from errors we hit while running it.
selenium · automation · java
7 MIN
Updated
A practical path to tests in CI: the GitHub Actions workflow Playwright generates and what each line does, the additions a real project needs (taken from this site's pipeline), and how to shard a slow suite and merge the results into one report.
ci cd · automation · github actions
9 MIN
Updated
A concrete comparison instead of a debate: which bugs on a deliberately broken demo shop an automated suite caught, which ones a person caught, and a short set of questions for deciding what to automate next.
qa · manual testing · automation
5 MIN
Updated
Create a Playwright project, write login and checkout tests for a real demo shop, see what a failing assertion looks like, and use fixtures and the trace viewer. Copy the code and it runs.
playwright · automation · javascript
8 MIN
Updated
Ten skills for testers, in the order they build on each other: test design, bug reporting, exploratory testing, API testing, one UI framework, Git and CI, test data and SQL, debugging failures, accessibility, and working with AI assistants. Each comes with a free project that proves you can do it.
qa career · skills · automation
7 MIN
Updated
Three rules for test data (own it, make it unique, clean it up) and the code that enforces them: a builder with safe defaults and a Playwright fixture whose cleanup runs even when a test fails. Includes the strategies for when you can't create data through an API.
test data · automation · strategy
7 MIN
Updated
Testing tools grouped by job: browser automation, API testing, BDD, accessibility, CI, test management, device clouds, and reporting. Each entry says what the tool is for, when you don't need it, and whether we've used it ourselves.
tools · qa · automation
7 MIN
Updated
Where the test pyramid comes from, the only widely cited ratios and what their authors said about them, the ice cream cone and hourglass antipatterns, and a rule for choosing the layer of each new test.
test pyramid · strategy · qa
7 MIN
Updated