commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell (JIRA)" <>
Subject [jira] Commented: (DIGESTER-117) Missing unit tests using ant and maven
Date Tue, 03 Jul 2007 21:35:04 GMT


Henri Yandell commented on DIGESTER-117:

Either run 'maven ant', or replace the existing test stuff with:

      <junit printsummary="true" showoutput="true" fork="yes" haltonfailure="${test.failonerror}">
        <classpath refid="test.classpath"/>
          <fileset dir="${test.home}">
            <include name="**/*"/>
            <include name="**/*"/>
            <include name="**/plugins/"/>
            <include name="**/"/>

Which should we do?

> Missing unit tests using ant and maven
> --------------------------------------
>                 Key: DIGESTER-117
>                 URL:
>             Project: Commons Digester
>          Issue Type: Bug
>    Affects Versions: 1.8
>            Reporter: Gail Badner
> Currently, 136 unit tests are run using maven and 149 unit tests are run using ant.
> The maven build uses the file patterns:
>         **/*
>         **/*
> which misses the following tests:
>         **/plugins/
>         **/
> After the missing tests are added to the maven build, 157 tests are executed.
> The ant build does not execute the following tests:
>         LocationTrackerTestCase
>         NamespaceSnapshotTestCase
>         OverlappingCallMethodRuleTestCase
> After the missing tests to the ant build, 157 tests are executed.
> I'm not sure how this should be fixed; should test cases that don't end in "Test" or
"TestCase" be renamed?
> When this is fixed, it would be nice if the junit ant task were used to run the tests
so that the JUnit report can be generated.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message