Nov 8th, 2010, 07:35 AM
I'm actually surprised it ever worked. I always use JobRepositoryTestUtils and JdbcTemplate to clean up after a Job integration test.
If you'd like to raise a JIRA ticket it might be a decent target for 3.0 to support a single transaction for testing jobs. It's not really a great idea for production use because jobs tend to run too long for a single transaction.
Nov 9th, 2010, 04:26 AM
Well, it might have been more luck than anything else since I assume that having more data than the commit size should blow up my test anyway.
Originally Posted by Dave Syer
I do agree with the statement about production but I'll think about it if it would be a good idea for integration/unit testing. If I can't find any (real) downsides I'll raise a JIRA ticket for this. I might actually develop a quick 'n dirty solution for unit testing myself.
Tags for this Thread