By Trevor Stokvis on February 22, 2017
I’m sure this scenario has happened to you: Out of the corner of your eye you notice your team’s QA engineer approaching with a confused look on her face. Suddenly, your heart starts to beat faster…
Most of you would start to dread the upcoming conversation. “What did I do wrong? It was working for me, I swear!” you think to yourself.
As she gets closer you start to become a little more honest with yourself: “Well, I guess I didn’t fully test all the use cases but she must know that I was on a tight deadline and testing takes forever.”
Let’s imagine a different scenario: She reaches your desk and says “All good! That new testing tool is paying dividends.”
You spend the rest of the day not being afraid of your team’s QA because you realize the impact that rapidly creating tests is having on your confidence to ship high quality code.
Reasons for testing usually fall into three categories:
- You’re doing what you’re told
- You’re super responsible
- You (like me) find that seeing a line of green “test-passed” circles in Android Studio incredibly satisfying