Cheers sorry for the slow reply. What I've just done is renamed
TestExpectationCollection to AbstractTestExpectationCollection so it
doesn't get included in the tests.
On Fri, 2004-05-14 at 14:08, to...@us... wrote:
> With the new build.xml the unit tests are running again.
>
> However they are failing now because ant tries to run
> test.mockobjects.TestExpectationCollection, which is an abstract class.
>
>
> Workaround: exclude it from the unit tests (as done in the attached patch)
>
>
> However I would prefer a more general mechanism for abstract test classes like this
> one, for example naming them 'AbstractTestXXX'.
>
> Any comments?
>
> Regards,
>
> Tomy
>
>
>
> ______________________________________________________________________
> Index: build.xml
> ===================================================================
> RCS file: /cvsroot/mockobjects/mockobjects-java/build.xml,v
> retrieving revision 1.41
> diff -u -w -b -r1.41 build.xml
> --- build.xml 27 Apr 2004 10:26:06 -0000 1.41
> +++ build.xml 28 Apr 2004 10:07:46 -0000
> @@ -221,6 +221,7 @@
> <fileset dir="${core.classes}">
> <include name="test/**/*Test*.class" />
> <exclude name="test/**/*Test*$*.class" />
> + <exclude name="test/**/TestExpectationCollection.class" />
> <exclude name="**/AllTests.class" />
> </fileset>
>
--
Jeff Martin
Memetic Engineer
http://www.custommonkey.org/
|