I just ran across jOOQ after searching for ways to mock JDBC access. Specifically, I am trying to test cross-database support for calling stored procedures. Mocking this up for unit testing makes a lot of sense to me before I move on to functional testing on the actual databases because there are certain baseline assumptions within which I'd like to test my code. For background, this is support I have developed in Hibernate both as a native API and for JPA 2.1 stored procedure support. So there is a certain set of parameters defined as to how the stored procedures are called and ultimately how the results are handled.
In general, how would you go about mocking out the calls to JDBC? Yes I have looked at the docs, but they all refer to having a physical schema in place and doing some form of reverse engineering from that schema. But I'd prefer to have no schema and just tell jOOQ exactly what to do from my mocks (aka, return a Result here, update counts there, mixed results for this other thing, etc). Could anyone point me to the docs that describe how I would go about that level of mocking, if that is possible? Or if there is no documentation for that use case yet, how would I go about it in general? Thanks! -- 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.
