Hi,

I want to unit test the persistence of a single object to the database, then rollback so the test works the next time as well. I'm having problems with the SaveOrUpdate method.

My scenario is:
- Begin transaction
- Retrieve object
- Change object property
- Save changes
- Clear cached objects
- Re-retrieve object
- Check object property changed
- Rollback transaction

This fails as the Save change step (calling ISession.SaveOrUpdate) didn't actually persist, and the ClearCache cancels the changes.

I don't want to use the ISession.Flush method as this doesn't really test the code I use - the ISession.SaveOrUpdate method. Similarly I don't want to commit the transaction as this would interfere with other tests.

Any ideas on how I can get around this?

Cheers

I don't have any suggestion, but IMO, you should avoid inter-dependency between unit tests as much as possible (though it can be hard if the initialization is "heavy").

This is a test of a single object (Order) which I retrieve, update a field (totalvalue) then save again to check the persistence of that field worked. If it depends on any other object I generally use EasyMock or nMock to reduce interdependancy on any external concerns.

Having said that, I've now read the hibernate 2.0.1 documentation which has explained that persistence is only done by the flush, commit or certain finds so I think what I'm seeking to do is impossible, and I'll just have to live with doing a flush.

Ah well.