The argument in favor of this is mostly – we want to deliver quickly and automation slows us down.
IMHO there are a couple of reasons for why this is the argument folks make:
– Definition of Done not defined
– Testability not built into the product architecture
– Automation is only the automation engineers job
– Automation is focused only on the UI
– Automation is considered only tester’s job..
If we agree with that, we are consciously making a decision to incur technical debt and have problems down the line.
To build your product well, you have to spend do things properly and upfront thinking.
Due to many reasons, a wide spread perception about testing has been ‘the blockers to release’,
Not just because of time, IMHO also because the internal goal of testers is somewhat ‘stop the release from going’!
Here how I’ve seen it happen:
– Testers have lots to cover, and less time
– Anything goes wrong in production, tester’s get blamed
– To avoid that situation, testers try to mount substantial evidence that there are risks in the release, so ‘Release at your own risk!’
The main problem here is NOT testers or testing – it’s this blame game mentality
To improve quality in such a setup, start working on build psychological safety first, rest will follow..
At what stage should you have automation and exploratory testing?
What testing practices will help us reduce number of issues & identify issues quicker?
What testing / quality related KPIs should we measure?
A test strategy is expected to answer many of these questions
Typical old school test strategies usually don’t speak directly to these pain points and are difficult to develop, use & maintain. To help teams design a test strategy that helps them TRANSFORM their practices over time – I designed the ‘DevOps Test Strategy Mindmap’ – DTSM
How to develop ‘collective’ ownership of quality?
One way is having a test strategy that speaks to everyone on the team. Every action taken by anyone in the team contributes to quality, knowingly or unknowingly, positively or negatively.
So it’s important to develop ways of working which improve quality of the product. In this talk I’m introducing a test strategy that accomplishes just that.