Test automation strategy: automating the right things
Suites get abandoned when they are slow, flaky or testing the wrong level. A deliberate strategy prevents all three.
Topic
Every article we have published on qa & testing.
Suites get abandoned when they are slow, flaky or testing the wrong level. A deliberate strategy prevents all three.
Performance tests answer specific questions. Running load without a question produces numbers nobody can act on.
API tests run faster than interface tests and break less often than unit tests when internals change. They are the most cost-effective layer for most systems.
Automated tools identify a portion of accessibility barriers. The rest need a person, a keyboard and a screen reader.
Most exploited vulnerabilities fall into a small number of well-understood categories. Testing for those systematically catches most of the risk.
The cost of a defect rises with how late it is found. Shifting testing earlier is mostly about involving testers before code exists.
Every regression suite eventually becomes slow and partly redundant. Managing that deliberately keeps it valuable.
Most QA reporting counts activity. A few measures actually describe quality and inform decisions.