I use hsqld and dbunit with Cayenne to run my unit and integration
tests. Nothing specific comes to mind. General things I did were to
use cgen to generate dbunit classes for programmically populating the
database tables (external to cayenne) and making sure my tests didn't
exceed the connection pool limits. I also turned off the connection
pool maintenance thread, but I don't remember why now.
I also like h2 but it doesn't run entirely in memory whereas hsqld
definitely does.
It's trivial to swap hsqld between totally isolated-and-in-memory and
in-memory-under-a-tcp-ip-server for those times when you need to use
another tool to see what the database looks like during a test.
<data-source>
<url value="jdbc:hsqldb:mem:TESTDB"/>
<url value="jdbc:hsqldb:hsql://localhost/TESTDB"/>
On Wed, May 2, 2018 at 3:59 PM, Ken Anderson
<[email protected]> wrote:
> All,
>
> We’re thinking about setting up an in-memory database in place of SQL Server
> for doing unit tests. Does anyone have any experience doing this with
> Cayenne? Any recommendations or warnings?
>
> Thanks,
> Ken
> Confidentiality Notice: This e-mail and accompanying documents contain
> confidential information intended for a specific individual and purpose. This
> e-mailed information is private and protected by law. If you are not the
> intended recipient, you are hereby notified that any disclosure, copying, or
> distribution, or the taking of any action based on the contents of this
> information, is strictly prohibited.
