Pencils Down

One of our developers had the following type of code in place:

Parent parent = new Parent();
dao.create(parent);
Child child = new Child();
parent.getChildren().add(child);
dao.saveOrUpdate(parent);
dao.create(child);


All of this code worked!  We never noticed the error until we put a Hibernate wrapper in play that has asserts for all kinds of extraneous conditions.  In the above code the child has not been created in Hibernate yet.

So, why did it work in straight Hibernate?  We think it didn’t work and only gave a silent error/exception.  All of this would be cleaned up later as a cleanup task by the create(child) call or the even later flush() call.

Of course, once we switched the order of the create(child) call with the saveOrUpdate(parent) it all worked.

We had noticed similar silent errors for delete() calls as well.

IBM offered to buy Sun at twice the going rate per share.  Sun baulked, supposedly based on wanting more money.  At first blush it sounds like the bonehead move of the year.  But then it doesn’t seem likely price is really the issue.

Sun has nice machines, but they are old school at this point.  Why not just buy a cheap Intel box that runs Linux?  No dealing with Solaris admins or costly hardware additions.

IBM has a good franchise in high-end machines so that seems like a good fit.  IBM has a definite commitment to Java across the company.  Again, a good fit

Overall it would seem this might be a good idea.

Then you start to think about the people at Sun versus the people at IBM: California dreaming vs. Armonk business blue suits.  There is just no way these people could get along.  The Sun people must have been starting protests in the halls as soon as the word got out.

One of our developers came up with some sample code like the following:

This error is a catchall for anything else that might be wrong with your test class.  First make sure any of the below problems are not occurring. 

Your unit test code is running JUnit4.  At least one test method must have the @Test annotation.  Otherwise this error occurs.

If the class you are testing has @Required setters for Spring injections they must be set otherwise JUnit will mask the missing required exception as a no runnable methods exception.

If you are initializing your mock objects outside of the @Begin method you will get this error.

If you are attempting to mock the same class more than once you will get this error.