I have to add lazy = true for the property & amp; I have added ant task to make the class intimate to enable hibernate to make laziness in my pom.
Is there a way to test that the property now runs the Hibernate SQL Console output without seeing the idle mode in runtime? I mean, with unit testing (using spring test with im junti) I do not want to test that the lazy attribute exists in XML mapping. It alone does not ensure that it will behave as a lazy property.
I am convinced that the bugs revealed by a tester will not appear more in the future (I am not in the project alone)
I follow (best?) Practice That there should not be any automatic test of every trivial fault to stop your coming time. (By the way, I have taken the idea from Spring Framework to test)
You can load the unit, session , And then emphasize that a LazyInitializationException
Comments
Post a Comment