Test Automation Anti-Patterns
Test Automation Anti-patterns:
There is enough data out there which explains what testing anti-patterns are, we will look at some of the most interesting test automation anti-patterns here:
The first one and the most important one is the right amount of UI testing in the testing pyramid:
- Whenever we talk to most stakeholders about test automation, they think about UI automation.
- "A team is doing too much UI automation when they are finding NPEs (Null pointer exceptions) via their UI automated tests."
- Manual Session based testing is a fancy way of saying exploratory testing
- Automated API tests are the best bang for the buck wrt tests that are easy to write and stable and a reliable signal.
- Integration Tests are always valuable; but we need to ration the number of integration tests one writes as they can be more difficult to debug and have a high noise factor due to all the moving pieces
- Automated component testing allows one to test a particular component (server) in isolation. you mock everything else out and ensure this component behaves as intended
A similar catalog has been created for anti-patterns in unit testing
Some other classic test automation anti-patterns:
Good read: http://qabok.com/tdd-patterns-and-anti-patterns/