Test Automation

This hub collects our engineering notes on test automation and unit testing, written for people who own a QA budget and need to decide what to automate first. We cover the mechanics of building reliable suites, from choosing between stubs and mocks to structuring assertions that survive refactors. If you are still setting overall QA policy rather than picking tools, our QA Process and Strategy hub is the better starting point.

Most teams start with unit testing fundamentals and practices before moving into browser and mobile automation, and we cover the tradeoffs involved in scaling web tests with Selenium. Flaky suites and false positives get their own coverage too, since a passing pipeline that lies to you is worse than no pipeline at all.

When a team needs test automation built out or an existing suite rescued from flakiness, our engineers take on the work directly through our test automation services, and for organizations standing up automated pipelines from scratch we also offer automated QA services scoped to your stack.

If you read only one article here, start with unit testing fundamentals and practices, since it frames the assumptions the rest of the hub builds on. It helps answer a common early decision: whether your team should invest in unit coverage before layering on browser or mobile automation.