4 ms·
TDD is great. It should be a given on any project that isn't just a spike. I'm curious what kind of products you were building? Simple websites, or full fledge
by ThatMightBePaul 11y ago
TDD is great. It should be a given on any project that isn't just a spike.
I'm curious what kind of products you were building? Simple websites, or full fledged applications?
100% unit test coverage can still miss a host of gnarly bugs. A lot of the ugliness of QA comes from how A interacts with B. Or how A + B + C + D work together. Or at least, that's my 2 cents :D
- geoelectric 11y agoYou also have to qualify 100% coverage: SUT lines, branches, or paths? Those are all very different levels of rigor. The two most useful code coverage stats I've found are 0 and "less than yesterday." The former tells me something pretty important about the culture of the team who owns that code; and having rules against the latter is about the only way to ensure a test-on-checkin policy.
- ThatMightBePaul 11y agoI love this metric, and am totally stealing it.
- geoelectric 11y agoAll yours!
- MichaelCrawford 11y agoI've done a wide variety of projects - cross-platform GUI, a windows database kernel implemented as a dll - that is, not a server - embedded storage firmware, mac os x device drivers (kernel extensions). For some but not all of my projects, failure was not an option. Imagine I lost a disk sector in my storage firmware.