If you say so. I think it wastes your time. Its your app, your use case. Much easier for you to whittle Spring out of the equation than me. How do I know what all those insidious little Spring annotations do? And in my opinion, its your responsibility to make sure its a problem with Hibernate, not mine, to be blunt. Thats part of the SSCCE exercise..

Basically what you are asking is how to bootstrap Hibernate, yeah? I mean at the end of the day, thats what your test case needs to do. Bootstrap Hibernate and perform this work. If thats what you need, sure, we have approximately 4,000+ exmaples in the hibernate-core testsuite alone. Here is the test I was using for this one:
https://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src/test/java/org/hibernate/test/annotations/derivedidentities/e1/b/specjmapid/ondemand/LazyLoadingTest.java

I don't really care if you leverage down to the number of sessions opened/closed, number of connections, etc. But it should just be the same basic structure:

1. bootstrap Hibernate (which leverages a class org.hibernate.testing.junit4.BaseCoreFunctionalTestCase from the hibernate-testing artifact if you wish to just reuse it).
2. create some data
3. do your assertions
4. drop your data