Hi, These articles about mocking your database get a lot of traction and generate many clicks, which is good:
http://blog.jooq.org/2013/02/20/easy-mocking-of-your-database http://architects.dzone.com/articles/easy-mocking-your-database-0 http://www.javacodegeeks.com/2013/02/easy-mocking-of-your-database.html I'm sure that there's room for follow-up articles, once best practices have been established, and once the feature-set is more complete. So let's list the features we'd want to have: - More meaningful input formats for MockFileDatabase - Pattern matching in MockFileDatabase - A DSL API for setting up tests. Aaron's suggestion is this one: > UserRecord testData = new UserRecord(): > ... set fields ... > factory = new JooqTestSetup(dialect, settings) > .query( "select A, LOT, OF, COLUMNS from ADM_USER where > ADM_USER.ADM_USER_ID = 1" ) > .shouldReturn( testData ); > > https://groups.google.com/d/msg/jooq-user/OQzuxbqk-w8/Q5wV3cxc3DYJ The above DSL should have the same features as the MockFileDatabase, just in a programmatic way. Also, it should be easy to define the outcome of batch and multi-result queries Are there any other features that would be immediately useful? Cheers Lukas -- 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/groups/opt_out.
