Anteater tests (was Re: on better release and version management)

[Guido Casper <gc...@s-und-n.de>]

Bertrand Delacretaz <bd...@codeconsult.ch> wrote:
> Le Mercredi, 10 sep 2003, à 11:26 Europe/Zurich, Reinhard Poetz a
> écrit
>>
>> ...Would it be enough to extend our Anteater scripts (see Guido's
>> mail) and
>> add Anteater to our codebase and include it automatically to our
>> build system? ...
>
> certainly a Good Thing it tests are not too hard to write - anteater
> tests things from the user's point of view which would make us very
> confident that things actually work.
>
>> ...BTW, unfortunatly the latest Anteater release needs Java 1.4.x ...
>
> Not too big a problem IMHO, as tests will probably not be required to
> do a normal build.

How about the following change to the build?
Uncomment the anteater-tests and remove the dependency of the test
target on the anteater-tests target, so that if you run 'build test'
only the unit tests are run. To run the Anteater tests you have to run
'build anteater-tests'. This in turn has a dependency on the
'block-anteater-tests' target that copies all anteater tests (located
in <block>/test/anteater) to 'build/test/anteater' where they are then
executed. The anteater-tests target starts with a big attention message
hinting to make sure the anteater.home property is correctly set.

So we can see how Anteater usage develops and decide later whether to
put Anteater into CVS.

Guido

Re: Anteater tests

[Bertrand Delacretaz <bd...@codeconsult.ch>]

Le Jeudi, 11 sep 2003, à 08:41 Europe/Zurich, Guido Casper a écrit :

> ...How about the following change to the build?
> Uncomment the anteater-tests and remove the dependency of the test
> target on the anteater-tests target, so that if you run 'build test'
> only the unit tests are run. To run the Anteater tests you have to run
> 'build anteater-tests'....

I'd just add a warning to "build test" indicating that the anteater 
tests must be run separately.

> ..This in turn has a dependency on the
> 'block-anteater-tests' target that copies all anteater tests (located
> in <block>/test/anteater) to 'build/test/anteater' where they are then
> executed. The anteater-tests target starts with a big attention message
> hinting to make sure the anteater.home property is correctly set.
>
> So we can see how Anteater usage develops and decide later whether to
> put Anteater into CVS.

Sounds good - make anteater tests fairly easy to run at first, then add 
anteater to CVS if people bite to it!

- Bertrand