Spring Testing Survival guide

If you have an application with thousand of beans, you must do unit testing but…Spring testing is boring, belive me.
A very complex Spring application usually have a lot of dependency: I had to manage over 3000 beans definitions in a production project right now.
Sometimes you want only to test a bit of it, and setting up a complete Spring Context will drive you crazy.
To avoid losing mind, my suggestion is to …cheat. Let’see how.
Continue reading “Spring Testing Survival guide”

Web Testing Tools

Testing is important.

Testing web interfaces is difficult, and often your consultant company prefer to suggest you a manual-based testing.
But is it so difficult to do automatic web testing using open source software?

Let’s give a look to two nice web testing software

Warning: this article is still in progress: it has been published for getting comments all around.

Continue reading “Web Testing Tools”

Edivad: how to use old JUnit3 tests with JUnit4

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.

by /home/edivad.

At Gioorgi.com we do not see the point of using Annotations, anyway, this is JDK 5 babies.
So, thank you edivad for your help on finding a way to run junit3 tests on junit4!