We have recently upgraded our code base from a 2005 version to the latest version of hibernate.
As a result of that, we’re seeing significantly reduced code coverage in a number of our packages. These packages are almost entirely POJOs mapped to hibernate objects, and the difference seems to be in the coverage of getters and setters. Most of these objects are not directly unit tested, so the previous coverage most have come from their usage in some integration test causing hibernate to hit these getters and setters.
Has anyone seen similar things happening? Has there been a change in the way hibernate populates those objects that could explain that?
Most of the fields are set to lazy=false so that’s probably out of question.
We are using testng, cobertura and jdk 1.6.
Has somebody changed something in the xml to change the access to field, e.g.
or globally like this?
By default hibernate’s access is set to property, so that should use accessors where they are provided.