Navigation
User login
Quote
Francis Bacon
The human understanding is no dry light, but receives infusion from the will and affections; which proceed sciences which may be called "sciences as one would." For what a man had rather were true he more readily believes. Therefore he rejects difficult things from impatience of research; sober things, because they narrow hope; the deeper things of nature, from superstition; the light of experience, from arrogance and pride; things not commonly believed, out of deference to the opinion of the vulgar. Numberless in short are the ways, and sometimes imperceptible, in which the affections color and infect the understanding.
Java Unit Testing with open source: JUnit
Wed, 04/03/2002 - 07:25 — charlie.collins
JUnit is a full featured "Regression Testing Framework" for java. JUnit is open source via the IBM Common Public License. JUnit is good stuff. Checkit via the link. http://www.junit.org
This work is licensed under a Creative Commons License.
1998-2008 temple of the screaming penguin
TotSP Search
Community
Chatter
- You don't need anything
1 sec ago - Hey nice article however, i
2 days 13 hours ago - Appreciation
4 days 9 hours ago - thanks for information...
6 days 6 hours ago - In total agreement on this one
2 weeks 17 hours ago - Suggested change to wrapper
2 weeks 4 days ago - Hmmmm...i jus called it and
2 weeks 4 days ago - I just quit!
2 weeks 4 days ago - Touche!
Pun intended.
2 weeks 6 days ago - Re-pricing the Touch
2 weeks 6 days ago
Popular content
Today's:
All time:
Last viewed:
- Trouble sorting through the SPIN? Ask Triumph.
- It's 106 miles to Chicago, we've got a full tank of gas, half a pack of cigarettes, it's dark, and we're wearing sunglasses
- Theme for 2008: Apple and Linux "safer, better, and cheaper to operate"
- Apple pulls the 10.2.8 update after it was avail for a day or so
- Topsy Turvy Day: Redhat in the black, McDs in the red
Comments
Re: Java Unit Testing with open source: JUnit
Does anyone here have any experience with using JUnit or more general automated unit testing?
About two years ago I decided to introduce automated unit testing in a mid-size Java-based project I managed. Unfortunatelly it didn't work out I was forced to drop it.
There where two main problems:
1. devs complained they had to spent lots of their time maintaning the testing code, as every change in the main code required changes in tests.
2. The majority of test failures turned out to be caused by bugs in tests, not in the main code.
I suppose our problem was caused by introducing unit testing too early in the project life cycle when we didn't have well defined APIs yet.
Anyone has different experiences/opinions?
-
Jarek