Re: [Cdk-devel] how to test for regressions?

[John M. <joh...@gm...>]

We could use a system property but this isn’t portable and also problematic. As test run in a forked “clean” VM they don’t, and shouldn’t, get the system props from the parent process. I think the best way to do this is probably with profiles, this would also makes sense for the coverage tests.

This means the slow tests need to physically separate (at class or package level) but forces one to think about good tests. Having a naming akin to Mol2ReaderIntegrationTest and Mol2ReaderTest would suffice. We should also consider moving more than is currently tagged as slow - with the exception of the reaction and smsd most modules are slowed down by only a couple of tests. I know I included some stress tests in the ring perception, isomorphism and hash that could be moved to a slower test set. 

Here’s an example of the profiles for integration tests.

http://solidsoft.wordpress.com/2011/11/02/run-fast-unit-tests-often-slow-integration-rarely-testng-and-maven-configuration-guide/

Thoughts?

John

On 6 Mar 2014, at 20:07, Egon Willighagen <ego...@gm...> wrote:

> John,
> 
> I started with applying the first CDK patches *after* the Maven
> merge... I removed the Maven2 install I had alongside Maven3, and it
> compiles fine now :)
> 
> Also the tests run fine, with:
> 
> mvn test -Dmaven.test.failure.ignore=true
> 
> This takes long (we should look into CDKTestCase.runSlowTests()), but
> I am wondering how I can get a simple summary that I use to compare
> before and after the patch, to see if regressions were introduced...
> 
> How do you do that?
> 
> Egon
> 
> -- 
> E.L. Willighagen
> Department of Bioinformatics - BiGCaT
> Maastricht University (http://www.bigcat.unimaas.nl/)
> Homepage: http://egonw.github.com/
> LinkedIn: http://se.linkedin.com/in/egonw
> Blog: http://chem-bla-ics.blogspot.com/
> PubList: http://www.citeulike.org/user/egonw/tag/papers
> ORCID: 0000-0001-7542-0286
> 
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works. 
> Faster operations. Version large binaries.  Built-in WAN optimization and the
> freedom to use Git, Perforce or both. Make the move to Perforce.
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Cdk-devel mailing list
> Cdk...@li...
> https://lists.sourceforge.net/lists/listinfo/cdk-devel