Monthly Archives: June 2012

Recently I posted my opinion about regression. Regression bugs are likely to occur on projects with a lot of legacy code. I consider legacy code as untested code. At the legacy coderetreat we used a small codebase (you can find it here). With that codebase we exercised in sessions to improve the code. The nice thing is that this is very similar with your daily job. You open up a project and you have to make changes in code you haven’t seen before and do not understand. In order to get a better understanding you… Read Article →

I hate it. You change something and you can’t tell if your change broke something in the system. If you’re lucky, you did not break anything. Or nobody noticed it. Next to that, on the same scale of luck, the potential bugs are found in the manual testing phase. But often there is no time to do all the regression testing by hand. It will take days and days, and the change you made looked so insignificant. It should go live. What could possibly go wrong?. Then it happens. You’re live, your changes work, but… Read Article →

Scroll To Top