This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
Well, as the error message says, you didn't provide the constructor getting a String argument. You will have to write one. It will probably just call the super constructor, passing on the String argument.
As an aside, it looks like you are manually building the test suite because the tests need to be executed in a certain order? Are you aware of the fact that this is a "test smell"?
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
A "smell" is always bad. "Test smell" is a backformation from Kent Beck's "code smell". A "smell" is an indication that something's wrong, and you should check into it.
In this case, the problem is that your tests aren't independent. If one fails, they're all going to fail, which reduces their diagnostic value and also makes it hard to add, remove, or refactor tests.
I realize that you've done it this way to reduce the number of connections made to your database -- but that's actually the problem right there: unit tests shouldn't be hitting a real database unless absolutely necessary. Introduce a persistence layer, and test against DAOs loaded from a file. Or if you are specifically testing database code, try to use something lighter-weight like HSQLDB so that you can afford to reconnect on each test.