May 24th, 2009, 10:34 PM
Do you use dbunit, or just rely on rolling back transactions?
When working on big database applications... do you use dbunit, or just rely on rolling back transactions?
I really like the speed of using annotation-based testing and rolling back the transactions after the test finishes... however, I don't like testing my application visually using a separate database and having to switch back and forth. I'd rather use the same database and application context. is dbunit a good solution, or just manage two separate contexts?
May 24th, 2009, 11:06 PM
I'm also noticing problems where mostly everything gets rollback... and then for some reason a delete does not rollback and screws with the state of the database. This is annoying since I have to then re-add everything manually ;( Sometimes things don't rollback when the code is buggy when I'm writing it and something is wrong, which is the reason for the tests in the first place.