When you don't run your JUnit tests...

...bad things will happen

Here's my tip for the day. If you have a set of JUnit tests, always run them when delivering new code or changes to existing code. Brown's 1st law of JUnit testing says that when you don't run them for even the smallest of changes, bad things will happen. And that's exactly what happened to me today.

2 lines of code changed + a quick delivery that skipped the JUnit tests = a broken system

Note to self : always run your JUnit tests regardless of how trivial the change is. ;-)



Re: When you don't run your JUnit tests...

I try to make them part of the build script so you can't not run them.

Re: When you don't run your JUnit tests...

Me too, but there are always ways around this. ;-)

Re: When you don't run your JUnit tests...

Maven 2 as a building mechanism.
Though its also not bullet proof...
every thing is bypassable right?

Add a comment Send a TrackBack