[
https://issues.apache.org/jira/browse/DIGESTER-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510005
]
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"/>
<batchtest>
<fileset dir="${test.home}">
<include name="**/*TestCase.java"/>
<include name="**/*Test.java"/>
<include name="**/plugins/TestAll.java"/>
<include name="**/TestFactoryCreate.java"/>
</fileset>
</batchtest>
</junit>
Which should we do?
> Missing unit tests using ant and maven
> --------------------------------------
>
> Key: DIGESTER-117
> URL: https://issues.apache.org/jira/browse/DIGESTER-117
> 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:
> **/*Test.java
> **/*TestCase.java
> which misses the following tests:
> **/plugins/TestAll.java
> **/TestFactoryCreate.java
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
