[Testtools] revised CppAD test

[Stefan Vigerske]

Hi,

I changed the specification of the CppAD tests in NBprojectConfig.py.
In CppAD/trunk one can now do "make test", which runs all available
tests, depending on which of the configure flags are set (see Brad's
mail below). So NBprojectConfig.py now specify to call make test.
Unfortunately, this currently breaks testing of CppAD/stable.
I hope I have not caused much trouble with that.

Best,
Stefan

-------- Original Message --------
Subject: Re: CppAD directory structure
Date: Mon, 1 Feb 2010 04:50:12 -0800 (PST)
From: Brad Bell <bradbell at apl.washington.edu>
To: Stefan Vigerske <stefan at math.hu-berlin.de>


I have implemented a
	make test
that goes through the subdirectories specified on the CppAD
configure line. The corresponding svn commit is
	https://projects.coin-or.org/CppAD/changeset/1640


The more configure options, the more tests. Here is the
list of options that include more tests:

	--with-Introduction
	--with-Example
	--with-TestMore
	--with-Speed
	ADOLC_DIR=AdolcDir
	FADAD_DIR=FadbadDir
	SACADO_DIR=SacadoDir
	IPOPT_DIR=IpoptDir

You can see a listing of the results for all the tests that were included
in the file test.log.


I plan to eventually add an automated test corresponding to the
configure command line option
	--with-PrintFor
but I have not yet done so.

The tricky part was to get the tests to abort if any failed and to have a
separate log of the test outputs
	test.log
and to have test.log grow with each partial result (so that one can track
progress). I like to run it as follows:
	make test >& make.log
Then, in another window, I can track the progress of make.log and
test.log.


On Sat, 30 Jan 2010, Stefan Vigerske wrote:

> Hi,
>
> Bradley Bell schrieb:
>> I usally do not use my google account for e-mail, but my Seanet account and
>> my UW account are both currently down.
>>
>>
>> OK
>> This makes sense. Would
>>     make testall
>> be OK.
>
> Yes.
>
>> What do the other projects use ?
>
> They have a make test that runs at least some basic tests.
> And then we have setup some extra project specific tests in the
> TestTools project configuration file. But this setup is usually
> independent of the flags used to configure a project, which makes this a
> bit tricky in your case.
> E.g., I could only either enable cppad_ipopt/test/test for everyone
> testing CppAD (even if he builds without IPOPT_DIR=...) or for nobody
> (as currently).
>
> Stefan
>
>>
>>
>> On 1/30/2010 9:27 AM, Stefan Vigerske wrote:
>>
>> Hi,
>>
>> I think the easiest for me (and other testers) would be if there could
>> be one makefile target in the base directory that runs all available
>> tests (test_more/test_more, example/example, cppad_ipopt/test/test),
>> e.g. "make alltests".
>> That should return 0 if everything is fine and nonzero if there was
>> something failing.
>> You think, that would be not too difficult to implement?
>> Then also changes in the directory structure would not matter.
>> Currently I think, cppad_ipopt is build, but the test is not run.
>>
>> Stefan
>>
>


-- 
Stefan Vigerske
Humboldt University Berlin, Numerical Mathematics
http://www.math.hu-berlin.de/~stefan