An Early Look at JUnit 4

An anonymous reader writes "Elliotte Harold, proclaimed 'obsessive code tester', took an early look at JUnit4 and shows how to best utilize the framework in your own projects. Many feel that this is one of the most important third-party Java libraries ever developed. It promises to simplify testing by exploiting Java 5's annotation feature to identify tests rather than relying on subclassing, reflection, and naming conventions."

I don't know if I am the only one thinking this...

[TheOtherAgentM]

Maybe I am the only one that understands this too... J-J-J... J UNIT!

Just when I'd almost gotten comfortable

[Elrac]

...with JUnit 3, they have to go and improve it. I'll be eating my heart out for a while, because my company will surely not go to Java 5 before Java 6 is out, so these mentioned features will not be available to me. And when they are, I'll have to change my modus operandi.

Actually: Nice work, guys. I'll probably appreciate this once I get a chance to use it and wrap my head around it.

JUnit4 ? Goddess ?

[karvind]

But wikipedia says Junit was a minor goddess [wikipedia.org].

Just kidding, JUnit [wikipedia.org], one with capital U.

Re:I don't know if I am the only one thinking this

[Anonymous Coward]

You must be that famous rapper's computer-geek brother, 50 GHz...

Re:Could we cut down at manager speak here

[iggymanz]

To recap in manager-speak, you're saying the utilization of utilize nets suboptimal perceptual leadership utility?

Your not the only one

[sideshow]

Maybe I am the only one that understands this too... J-J-J... J UNIT!

Envy me, I'm programming's MVP!

Re:The Holy Grail

[KenSeymour]

The system I am looking for would use microphones to record all the conversations regarding requirements, resolve them into structured documents, then generate unit tests for all the requirements.

It would have to use microphones because, in my experience, you don't get a written requirements spec. Or if you do, customers don't feel constrained by it.

It would also have to raise a red flag when the customer contradicts themselves in the same sentence or paragraph.

But all kidding aside, JUnit is cool.
For intricate portions of my code I write tests that represent specific scenarios and run regression tests whenever I have finished implementing the new rule of the day.

Re:The Holy Grail

[willCode4Beer.com]

I say the holy grail is combining unit testing with genetic algorithms.
Then you just write the tests and let the code "evolve" until it passes them. Meanwhile, you get to sit around and drink beer.

Re:Your not the only one

[meadowsp]

MVC surely?