Test coverage percentage means shit. There, I said it, and it feels good to say something that my brain can relate to. Now to explain it, with a bit of background: Unit tests, like everybody knows, are meant to test small parts/modules/components of the code in isolation.
One thing in common with all types of tests is that (*duh*) they are supposed to make sure that the module/application behaves the way it was designed/thought of. Does this mean that making sure that every line of code is currently being tested? Hell no!
by
stargaming
2008-10-09 06:04
testing