I recently stumbled upon a question on Stack overflow, that actually intrigued me and made me write an article on “why you should write a test for every bug”.
The person’s question was: Should I write a small test for every bug / defect /ticket ?
Response from StackExchange, testing community:
“I do not create a new test case for every bug. I believe testing is about managing risk. If I believe the risk of a a bug reappearing is low, I will test the bug when the developer says it is fixed, but I will not re-test it for every subsequent release. Judging risk is subjective, and sometimes my judgement is wrong, but I think this way of testing is a better use of resources than testing for every bug that has ever appeared.
Other organizations may manage risk differently because of the nature of their business, their regulatory environment, or the culture of the company.” source.
My answer, is yes! you should definitely write a test for every defect.
I do advertise writing as many test cases as possible. If you find a defect, you definitely must write an automated test scenario for it!
Simple. If a bug occurred once, it will occur again.
The developer told you that the bug it’s fixed, right? How can they know it will never trigger again?
In my testing experience, I’ve noticed that a bug that reproduced once, it will reproduce again. Software development, is difficult. Asserting developers’s job is even more difficult.
Let’s have the question subjectively:
Should you write a test for every bug ?
Yes. Because is better to be safe, test every small bit and make sure that everything works than to lose money because you have not verified that enough that everything works.
Testing is about managing risks. – half right…
Testing helps managing the risk. You can manage, and lower that risk, by test it.
You can make sure and minimize any risks with your application, by actually testing it! How can you be certain that a bugs will not occur ? You can’t. 🙂
Nobody can give the guarantee that an issue will not reproduce again. And if it does reproduce again, you will want your developers to know that before your customers. for that, you’re going to need an automation tester, and some automated testing done, for your application.
Another article that I liked : http://www.requirementdriventesting.com/software-test-methodology-rdtrule4/
Each defect should have one requirement and test case – that is absolutely correct, Sir!
Are you interested in someone automated writing test scripts for you ?
get in touch with me, I will help with automation testing. You can contact me, here.