Well, I've searched a bit on mailing list and found some posts about testing,
Like this one: https://groups.google.com/forum/m/#!searchin/jooq-user/Dataset/jooq-user/SHoA9GA2MwE Other posts are mocking database layer, and yes it is interesting and useful in some scenarios, but I found this approach too much time consuming (developing time) so my question is regarding database integration testing. I don't care too much that my tests could be slow (execution time). Execution time could be handled with an appropriate continuous integration cluster. Usually my approach is to create programmatically a minimal fixture/dataset per test method (a test method is a specific aspect), and yes this is time consuming but I found useful for several reasons: - if I found dataset too complex to setup, maybe the scenario should be splitted - I'm focused to thinking about edge case Create manually a minimal dataset could be easily a pain in the ass, but creating it programmatically in a smart way (taking care of phisical database constraints: not null, unique, foreign key) almost completely hide this aspect. Obviously I'm not talking about a domain aware dataset generator. For my needs having jooq dataset setup facilities and, why not, dataset assertion (probably in a dedicated module, maybe with external dependency like hamcrest/assertj) would be very nice. What do you think about it? -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
