kasia in a nutshell

I was writing some test classes at work today using JUnit.. nothing out of the ordinary.. just your typical..

result = doSomething();
assert(expected == result);

I'm sure someone's already spotted my problem.. but wait :)

Code compiled.. that's nice.. then a co-worker cannot compile it in her work area. Hm. Problem. Apparently assert(boolean) is not a valid JUnit method call.. What? Checked my libraries.. sure enough mine's horribly out of date, hers is newer.

Now I'm mad. You don't just remove a call.. you deprecate it! My compiler didn't give me a deprecation warning.. (as you can imagine I was already salivating at the prospect of having a good rant at JUnit's expense). Checked their website.. read documentation (yah, I do that sometimes, but only when absolutely necessary) and found out that since assert has been assimilated by Sun as a Java keyword, the method call was deprecated and since removed.. A long-ass time ago.

My jar file was *really* out of date. (This is where I slap my forehead and you laugh at my expense).