For me, my integration tests are all against hsqldb and my deployments are all against Oracle. I use h2 instead for my non-Cayenne project for a dev deployment, but for testing, hsqldb seems to do a better job. I'd like to use H2 as a dev deployment in my cayenne project as well, but I've never gotten around to setting it up (building a selective data migrator from production to dev).
On Tue, Nov 25, 2014 at 7:59 AM, Aristedes Maniatis <[email protected]> wrote: > On 25/11/2014 10:52pm, Andrus Adamchik wrote: >> Many thanks to Savva Kolbachev for the effort to reorganize our test suite >> and implement a sound algorithm for maintaining test DB consistency without >> sacrificing the performance. With this big randomness factor out of the >> picture we have a good chance of maintaining the builds in the blue going >> forward. > > That's terrific. Well done. That will also make it much easier to handle pull > requests from github which will automatically be tested. > > I guess next is to see what other databases we can test against. Does anyone > know what databases are available in the Apache build cluster? Oracle, mysql, > postgresql and MS-SQL are probably the most important targets. > > This also provides a good base to review code coverage, and I've just put in > a request to Sonar to move our repo from svn to git: > http://nemo.sonarqube.org/dashboard/index/org.apache.cayenne:cayenne-parent > > Ari > > > -- > --------------------------> > Aristedes Maniatis > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
