Quote:
Originally Posted by Gullanian
I think this is ok but it's good to be aware that fixes can have a domino effect on other parts of code so testing might need to be broader than that depending on the nature of the original bug.
The reason you should write tests for every bug IMO is because:
A bug must originate from an area of the code that did not have a test (or had a bad test), otherwise it would have been picked up when running the tests.
Therefore, once the bug is fixed, you need to write a test to fill in the hole in your testing suite. Then you
must run the entire test suite. If you do not do this then your testing is essentially pointless.
If the bug you have just fixed breaks code in a different area of the application, the tests will pick it up.
---
I think that its better to just think of bugs as holes in your testing framework.