Yeah, I completely understand, plus in-memory is faster. I never got
ambitious enough to make it more configurable so I could pick which
location for which test. Ideally, when a test is stable, it should run
in-memory, but I still liked the forensics of on-disk.
On Wed, May 2, 2018 at 5:40 PM M
The reason I went with having the db entirely in memory was to run
tests in parallel. Once you have a disk presence, you'll have to
worry about test collisions.
On Wed, May 2, 2018 at 5:35 PM, Michael Gentry wrote:
> Hi Ken,
>
> To add to what Mike said, I've used H2 in the past with pretty good
Hi Ken,
To add to what Mike said, I've used H2 in the past with pretty good
results. You can either let Cayenne create your schema or use something
like Flyway/Liquibase if you have that integrated into your application
already.
One thing I do differently, though, is I create a temporary on-disk
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
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 in
