One of the most significant issues I often see in automation is lack of goals.
Team do automation write lots and lots of tests. But they will never consider if their test or automation is coming closer to their goal.
Brent from AB Testing podcast likes to say „Customer don’t buy software they buy the solution to their problem”.
I like to think the same thing goes for automation we shouldn’t buy „just automation” what we want to buy/make is the solution to our problem.
I am going to steal and repurpose another quote from AB testing, and I will say: Thay your overarching goal of automation should be „Accelerate the Achievement of Shippable Quality.”
But this is a vague high-level goal for each solution/automation project you want to have a more detailed goal. And then when you are writing each and every test, you should ask yourself: „Is this helping me to achieve our goals”?
You would be surprised how often the answer will be – no this test won’t, or there is a better test to write.
Here lies the hardest part, having enough discipline to admit what you do is not the best thing you could do.
I have experienced that! Not too long ago, I caught my self-doing very convoluted explanation to myself why the actions I am taking are actually helping me achieve my goals! And here’s a hint if you can’t explain it in a straightforward sentence, you probably are lying to yourself
So why I am not presenting you any example goals?
Cause I am hoping for discussion under this post 🙂
Present me your proposition, and then we will discuss them.
If you want more 300 you can read it here.