Technologies
The instruments, and what each one is bad at
Every tool below is one we actually reach for. Each page says what it is good at, where it stops being the right answer, and what we pair it with — because a tool list without trade-offs tells you nothing about whether the people holding it know when not to use it.
How we choose
Mostly by what the team inherits. A suite written in a tool nobody at the client can read is a suite that stops being maintained the month after handover, so the deciding question is usually which instrument your engineers will still be comfortable extending in a year, not which one benchmarks best.
After that it comes down to what the tool removes rather than what it adds. Auto-waiting removes the single largest source of flakiness in browser automation. A real programming model removes the ceiling that record-and-playback hits on the second refactor. An exit code removes the need for a person to interpret a graph before a pipeline can make a decision.
We are not loyal to any of them. Where a tool is the wrong fit we say so, including when the right answer is one we do not use.
Test automation
- PlaywrightBrowser automation with waiting built into every action.
- CypressA test runner that executes inside the page itself.
- SeleniumThe WebDriver standard, and everything built on top.
- WebdriverIOA Node framework covering browsers and native apps.
- AppiumThe WebDriver protocol, pointed at native mobile applications.
Contact
Not sure which of these you need?
Tell us what you are trying to verify and on what timeline. The recommendation is free, and sometimes it is that you do not need us.