Quality Assurance Practice Story
Once upon a time, there were two friends Mike and Jake got an idea to develop a smartwatch that will record people movements, and at the same time keep record of their blood pressure, and heart rate. They decided to work on the project separately. So, they started. Both of them developed plans how to do it and put their plans in action. They gathered everything that they needed and started working on achieving what they have imagined.
After one month, Mike has already finished the project, while Jake was still testing his product. Mike laughed at Jake because he was done with his project, and Jake was still in the process of doing it. After two months all was ready. They sat in a coffee bar and said let’s try the smartwatches. Mike was the first to try his project. He turned it on and started walking around the coffee bar, and Oops! Something terrible happened – the smartwatch wasn’t functioning as it was supposed to, it didn’t count the steps accurately, and moreover it showed incorrect number for the heart rate.
And now it was Jake’s turn. He did the same that Mike did and everything worked perfectly. Jake sat back and they had a small talk with Mike. After all, Mike understood that the testing measures that Jake undertook were the reasons for his successful project. And he decided to start over, but this time testing every step that he makes.
Lesson learned: If you forget to test, and not just the end-result, but also during the process of development, you might end up with a product which nearly satisfy your requirements, let alone your clients’ requirements and needs.