It’s been a long time I’m not posting but just changed job and relocated abroad, so no time for the blog.
During these weeks I was too busy for contributing the weekly link. Here it is one for this week 🙂
…But Maven needs a proper and clean environment…
Following the recommendations of Corey Haines, Michael Guterl, James Martin and Michael Hunger I decided to get Kent Beck’s screencasts on Test Driven Development which have been published by the Pragmatic Programmers.
REST Web Services can be particularly difficult to test, with the need for networking, a web container, multiple threads and transaction management creating extra complexity beyond your standard unit test. In this article I demonstrate patterns designed to address this complexity while enabling complete testing of your REST web service stack.
No. One word, a complete sentence. We all learned to say it around our first birthday, so why do we have such a hard time saying it now when it comes to our work?
Every meeting is an opportunity. Why waste your first one?
JDBC is more than a background player in database connectivity. The more you know about it, the more efficient your RDBMS interactions will be.
Again talking about JUnit 4. I’m used to use TestSuite to group tests. And add them to the AllTests class. In JUnit 4 it’s quite similar to the 3.x method, just using Java Annotation instead of the old TestSuite class.
Here is the pdf with the example code for having a TestSuite of TestSuite in JUnit 4.
Finally even me landed in the JUnit 4 planet.
The main difficulty in migration from 3.8.* is the class AllTests : a class with all the tests in it from where you can run all application tests in one shot.
The 4.x way is to use JDK (>=5) annotation, but if you for some reason have to use the JDK 1.4 you have two solutions. The one I prefer is to use junit 3.8.x but if you cannot tolerate the missing of JUnit 4.x in the attached PDF you’ll find the standard 4.x way (with annotation) and a workaround for using the old JUnit TestSuite syntax.