Comments on: An Intro into Test Driven Development with JUnit4

By: uberVU - social comments

uberVU - social comments — Wed, 04 Nov 2009 00:33:23 +0000

Social comments and analytics for this post…

This post was mentioned on Twitter by TurnleafDesign: Rambling on: An Intro into Test Driven Development with JUnit4 http://www.turnleafdesign.com/?p=260…

By: An Intro into Test Driven Development with JUnit4 « Jasper Blog

An Intro into Test Driven Development with JUnit4 « Jasper Blog — Wed, 28 Oct 2009 08:55:09 +0000

[...] Read more: TURNLEAF DESIGN [...]

By: Paul

Paul — Tue, 27 Oct 2009 19:01:58 +0000

Well, the @Test annotation tells you it’s a test.
Extending TestCase, in addition, seems redundant

Give a little reading on “Composition over inheritance”.

A minor criticism, when possible try to avoid the not (!) operator in your tests.
For example, instead of:
Assert.assertTrue(!forecasts.isEmpty());
do:
Assert.assertFalse(forecasts.isEmpty());

Later, when folks are reading the code, it’s really easy to miss those.

By: Billy Korando

Billy Korando — Tue, 27 Oct 2009 13:43:04 +0000

Yea I was thinking of doing a static import, but it still seems that a Junit class should import TestClass, since it is a type of test class.

By: IBBoard

IBBoard — Tue, 27 Oct 2009 09:28:24 +0000

“For some dumb reason when you create a new Junit4 test class in Eclipse it does not automatically inherit TestClass. Anyways I inherit that class now so you can just do assertEquals(expected, actual) instead of Assert.assertEquals(expected, actual).”

If you’re using Java 1.5 or later (and why not? Generics are extremely useful) then why not just use the static imports? Go to the Eclipse preferences then Java > Editor > Content Assist > Favorites and add “junit.framework.Assert.*”, then make sure “Use static imports” is checked in Java > Editor > Content Assist and Eclipse will auto-complete “assertEquals” for you and include the static import.

Overall it looks like an interesting start to an article, but I’d probably have started TDD with something a little simpler than trying to do database connections (especially since unit tests that have a database backend are best not connecting to a database for consistency reasons – although the connector itself may be a different matter).