jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jukka Zitting <jukka.zitt...@gmail.com>
Subject Jackrabbit integration tests in a separate component
Date Thu, 02 Jul 2009 13:00:25 GMT
Hi,

I'd like to introduce a separate jackrabbit-it component where we
could put any long-running integration tests that don't need to be run
per each commit. This component would be included in the build only
when a special "it" profile is enabled.

Hudson would be configured to always include these integration tests
and they would also be a mandatory part of the release process.

This would help speed up the default build that IMHO still takes too long:

    $ mvn clean install
    [...]
    [INFO] ------------------------------------------------------------------------
    [INFO] Reactor Summary:
    [INFO] ------------------------------------------------------------------------
    [INFO] Jackrabbit Parent POM .................................
SUCCESS [2.998s]
    [INFO] Jackrabbit API ........................................
SUCCESS [2.298s]
    [INFO] Jackrabbit JCR Commons ................................
SUCCESS [12.933s]
    [INFO] Jackrabbit JCR Tests ..................................
SUCCESS [5.065s]
    [INFO] Jackrabbit SPI ........................................
SUCCESS [1.775s]
    [INFO] Jackrabbit SPI Commons ................................
SUCCESS [11.281s]
    [INFO] Jackrabbit Text Extractors ............................
SUCCESS [2.708s]
    [INFO] Jackrabbit Core .......................................
SUCCESS [3:37.721s]
    [INFO] Jackrabbit WebDAV Library .............................
SUCCESS [3.979s]
    [INFO] Jackrabbit JCR Server .................................
SUCCESS [3.350s]
    [INFO] Jackrabbit Web Application ............................
SUCCESS [6.040s]
    [INFO] Jackrabbit JCA Resource Adapter .......................
SUCCESS [9.891s]
    [INFO] Jackrabbit JCR to SPI .................................
SUCCESS [5.178s]
    [INFO] Jackrabbit SPI to JCR .................................
SUCCESS [1:34.015s]
    [INFO] Jackrabbit SPI to WebDAV ..............................
SUCCESS [2.435s]
    [INFO] Jackrabbit JCR Client .................................
SUCCESS [3.989s]
    [INFO] Jackrabbit Standalone .................................
SUCCESS [1:00.324s]
    [INFO] Apache Jackrabbit .....................................
SUCCESS [2.184s]
    [INFO] ------------------------------------------------------------------------
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD SUCCESSFUL
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 7 minutes 28 seconds
    [INFO] Finished at: Thu Jul 02 14:49:51 CEST 2009
    [INFO] Final Memory: 90M/546M
    [INFO] ------------------------------------------------------------------------

The big question is of course whether we should move the TCK tests
away from the default build to the integration tests. Currently the
TCK takes about 75 seconds on my desktop and the default build runs it
twice, once for core and once for spi2jcr.

BR,

Jukka Zitting

Mime
View raw message