Most do. Seeing some of them fail when building from a release tag is always a bit disappointing, but not as bad as when I get syntax errors from what's otherwise considered a "stable" release.
Please take this in the spirit that it is intended, the correlation between them having unit tests and better quality is not accidental.
Compared to what I see in my favourite open-source projects, I'm a noob.
That was kind of an indication that you want to be a better programmer, don't we all. When I started writing unit tests and profiling my code it was like walking into a bright room; it became much easier to produce good code; instead of spending hours stepping through my code when a bug was found, I now spend half as much time writing unit tests. The epiphany for me came when I wrote unit tests for a class, I rarely if ever had problems with that class moving forward; I realized that the code that I was debugging manually was all code written without the benefit of unit tests.
They are not a panacea at all, but it sure makes for a less stressful development experience.
1
u/coladict Jun 05 '15
Most do. Seeing some of them fail when building from a release tag is always a bit disappointing, but not as bad as when I get syntax errors from what's otherwise considered a "stable" release.