[jbossws-dev] [Design of JBoss Web Services] - Re: JBossWS Test Approach

[richard.opalka@jboss.com]

"richard.opalka at jboss.com" wrote : it's error prone approach
We're using maven surefire plugin to invoke our junit integration tests.
The problem is our tests are not just java component tests but they test whole
JBossWS integration to JBossAS. The concrete problem is we're using maven
dependencies mechanism to configure our tests classpath.
Unfortunately this introduces many defects to our tests:


  We're not testing AS using AS provided libraries in distribution
  We're using libraries from local maven repository where
  
    many of these libraries has wrong version (because of outdated dependency exclusions)
    we don't have control over which version of particular component jar will
        be used for testing when there are two libraries of the
        same component with different version.
        The only way to achieve it is to use maven
        dependency exclusions (a lot of work without any evident added value).
        These exclusions should be updated on daily basis when testing
        AS moving branches/trunks.
    we're using out of date libraries for moving AS versions - many updates
        of the required dependencies are not released to the maven repository
        To solve this AS maven artifacts (SNAPSHOTS) should be uploaded to maven repo on daily basis.
  



View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215196#4215196

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215196