Comments on: How Much Testing Is Enough?

By: Simca

Simca — Fri, 11 Sep 2009 01:27:21 +0000

Right now i just using unit test for testing.

By: What Does Your Development Environment Look Like? | Regular Geek

What Does Your Development Environment Look Like? | Regular Geek — Tue, 14 Jul 2009 12:42:53 +0000

[...] may seem a little off, but the idea is that you need to know if you have left something untested. My understanding is that you want to achieve over 90% test coverage, and hopefully about 95%. That last 5% is [...]

By: shahryar ghazi

shahryar ghazi — Tue, 16 Jun 2009 11:45:59 +0000

thanks for sharing … very helpful indeed

By: robdiana

robdiana — Mon, 15 Jun 2009 17:53:13 +0000

Julio

I definitely agree that you need higher level and lower level tests. The question of test coverage is not whether you are testing anything, but more that the test coverage does not need to be as complete as the lower levels.

At the “system” level, you do not want to try to get 90% code coverage because that would be tremendously difficult to do. However, at the system level you do want 90% or even 100% requirement coverage.

By: robdiana

robdiana — Mon, 15 Jun 2009 17:50:04 +0000

Tracy

The basic idea, which I did not really include, is that all of the tests are based on requirements. Admittedly, I completely assumed that part. Unit tests are really only helpful if they test something that someone has identified as a requirement, or it is a programmer requirement. If there is no requirement for what you are writing, why are you writing it?

By: julio

julio — Mon, 15 Jun 2009 17:39:53 +0000

lower and higher level tests, both are a must have. It’s not a either-or situation. To use a cooking analogy. Unit testing is making sure you have the best and freshest ingredients before you start the cooking. Functional and accepting testing is at a higher level, while your dish is starting to take shape.

Well, I know that in cooking as in programming, I need both levels of testing.

By: Tracy Harms

Tracy Harms — Mon, 15 Jun 2009 17:38:11 +0000

Tests help only insofar as they fit the requirements. One concern I have with TDD is how little attention it seems to put toward identifying output requirements.

Does TDD build on an existing discipline of determining output requirements? I’d be surprised if such a discipline could be quietly implied. Instead, I expect a lot of overt attention must go toward the processes of identifying what the software must do.

By: Ber2

Ber2 — Mon, 15 Jun 2009 03:43:23 +0000

Great article. Thanks for the sharing.