Unit testing a Hibernate driven application? [closed]

Answer 1

Two cases are easy to test:

1. When practical, perform your various calculations and transformations in functions that don't know about saving or loading entities. If you can make these pure functions, so much better.

2. For functions that only save to the database without reading from it, you can choose not to save when testing.

The simplest (crudest) way to do #2 is by adding a reallyUpdate parameter to the function, then surrounding each "save" call with:

if (reallyUpdate) {
    HibernateUtil.saveOrUpdate(theThing);
}

For me these were the lowest hanging fruit.