Comments on: How much testing is enough?

By: yonatan

yonatan — Sun, 26 Jul 2009 17:05:58 +0000

Yaron: I agree about simple tests (preferably a test method per single behavior of a single method in the class being tested) – although it can be frustrating having to refactor your unit tests along with your code, usually I think you need to write tests / make the tests pass after a refactoring anyway, so the price isn’t so big.
imho integration tests don’t help you refactor as well, they are more suitable for when you already have a feature working and wanna make sure it’s according to spec and that it stays ok. you can also make them more configurable so your clients can add cases without coding and recompiling (see fitness etc)

By: Yaron Naveh

Yaron Naveh — Sat, 25 Jul 2009 20:58:54 +0000

The easy tests I actually do the “test-first” way – write them before the code.

I sometimes do it also for more “complex” tests – but we have to be careful here: In my current project many features are agile in their nature and changes in api (or even functionality) are not rare. Maintaining tests for “agile” features can be very frustrating, especially when I need to explain my peers why tweaking a simple method functionality takes more than a second…

By: ripper234

ripper234 — Sat, 11 Jul 2009 19:20:04 +0000

We don’t usually use code coverage tools. I personally try to write tests for the meaningful/complex features, and the tests that are easy to write. You probably don’t want to write tests that are both difficult to write and maintain and are sure to pass – but it’s not always easy to spot them in advance.

By: Boaz

Boaz — Sat, 11 Jul 2009 17:03:22 +0000

Also, how do you know your code is well tested? Do you just think/write all the tests you want to write that test every feature of your code? Do you rely on code coverage?