Test data management: the invisible bottleneck of automation
Most flaky tests don't fail because of logic, but because of data. Fixtures, factories, isolation, and the rule that each test owns its own state.
Articles on Software Quality, test automation, CI/CD, development, and readings that helped me along the way. Filter by topic below.
No articles found for your search.
Most flaky tests don't fail because of logic, but because of data. Fixtures, factories, isolation, and the rule that each test owns its own state.
The E2E run is green and yet the button vanished, the layout overflowed, or the text became invisible. How to compare screenshots, tame false positives, and fit it into the pipeline.
axe finds about a third of the problems; the rest is keyboard, screen reader, and human judgment. WCAG, tools, and the layered process that combines both.
Automating an app is not automating a website. How Appium works, native locators, device fragmentation, and the gestures, waits, and permissions that only exist on mobile.
Working is not the same as holding up. Load, stress, soak, and spike, plus the metrics that really matter (percentiles, throughput, and error rate) with a minimal JMeter plan.
The three most confused acronyms in QA. Which level each one works at, who writes it, and how they complement each other day to day, with a mind map and examples.
The language business and automation read the same way. Syntax, Scenario Outline, step definitions, and the anti-patterns that make scenarios brittle.
Equivalence partitioning, boundary values, decision tables, and state transitions: how to pick the right cases instead of trying to test everything.
Where each type of test lives, the ice cream cone anti-pattern, and how the Agile Testing quadrants reveal what nobody is covering.
What each term really means, when to run each one in the pipeline, and why retest and regression answer different questions.
The five test doubles, with code. The difference between stub and mock, and the split that matters: verifying state vs. verifying behavior.
Testing by thinking, not by following a script. Charters, time-boxed sessions, and heuristics (SFDPOT, RCRCRC) that give structure to investigation.
Why Playwright became my default for end-to-end tests: auto-wait, multi-browser, trace viewer, and fast parallel execution.
How to integrate automated tests into the pipeline, give the team fast feedback, and use quality gates to block regressions.
QA is not a phase or a department; it's a culture. Reflections on shift-left, prevention, and the role of the modern QA.
What makes a good unit test, the AAA pattern, what NOT to test, and why they are the highest-return investment in quality.
Contracts, status codes, schema validation, and how to bring your Postman collections into the pipeline with Newman.
How statistics, stripped of its complexity, becomes a powerful tool for decisions in BA and QA.
The pattern that keeps your automation from turning into a web of duplicated selectors. Practical rules to keep the suite readable and cheap.
Where flakiness comes from and how to fight it before the team loses trust in a green CI.
The anatomy of a report that leads to a quick fix: steps, evidence, context, and the difference between severity and priority.
Writing the test before the code feels counterintuitive, and it is one of the techniques that most improves the design of what you ship.
The confidence of integration with the speed of a unit test. How Pact guarantees the contract between consumer and provider.
Test code is code too. The principles from Robert C. Martin's book applied to an automation suite that lasts.