From: guido Date: Tue, 19 Apr 2005 14:59:19 +0000 (+0000) Subject: add information for build tests X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=64a9f1ba57bc0f15ed2606ac6b80fb3fd38d952b;p=dealii-svn.git add information for build tests git-svn-id: https://svn.dealii.org/trunk@10529 0785d39b-7218-0410-832d-ea1e28bc413d --- diff --git a/deal.II/doc/development/testsuite.html b/deal.II/doc/development/testsuite.html index e2384cd2b6..9a7d9e9814 100644 --- a/deal.II/doc/development/testsuite.html +++ b/deal.II/doc/development/testsuite.html @@ -15,6 +15,65 @@

The deal.II Testsuite

+ +

The deal.II testsuite consists of two parts, the build tests and + the regression tests. While the build tests just check if the + library can be compiled on different systems, the regression tests + actually are actually run and compare the output of the testy + programs with precomputed values. These two testsuites are + described below.

+ +

The build tests

+ +

With our build tests, we check if deal.II can be compiled on + different systems and with different compilers as well as + different configuration options. Results are collected in a + database and can be accessed online.

+ +

Running the build test suite is simple and we encourage deal.II + users with configurations not found on the build test page to + participate. Assuming you checked out deal.II into the directory + dealtest, running it is as simple as:

+ +
+
+    cd dealtest
+    make clean
+    cvs update -d -P
+    make build-test BUILDTESTFLAGS='-with-umfpack -with-lapack'
+    mail build-tests@dealii.org < build-test-log
+
+    
+ +

After cleaning up the directory and updating the library to the + most recent version, the make command configures the + library (here for use of UMFPack and LAPACK libraries) and + compiles everything. The result is in the file + build-test-log, Which is sent to the build test demon + in the end.

+ +

Configuring for a special compiler

+ +

If your compiler is not in the standard path or has a strange + name (like mycc for C and myCC for C++), + your template would be something like this:

+ +
+
+    export PATH=/my/compiler/path:$PATH
+    
+    cd dealtest
+    make clean
+    cvs update -d -P
+    make build-test BUILDTESTFLAGS='CC=mycc CXX=myCC'
+    mail build-tests@dealii.org < build-test-log
+
+    
+ + +

The regression tests

deal.II has a testsuite that, at the time this article is written, @@ -39,7 +98,7 @@

-

Running it

+

Running it

To run the testsuite, you first need CVS access to our source @@ -207,7 +266,7 @@ -

Adding new tests

+

Adding new tests

As mentioned above, we usually add a new test these days every @@ -218,7 +277,7 @@ .

-

The testcase

+

The testcase

For the testcase, we usually start from a template like this:

@@ -288,7 +347,7 @@ int main ()
     

-

An entry in the Makefile

+

An entry in the Makefile

In order for the Makefiles to pick up your new test, you have to @@ -315,7 +374,7 @@ int main () -

An expected output

+

An expected output

If you run your new test executable, you will get an output file @@ -368,7 +427,7 @@ int main () -

Checking in

+

Checking in

Tests are a way to make sure everything keeps working. If they @@ -389,7 +448,7 @@ int main ()

-

Adding a new system

+

Adding a new system

If you are working on a system or with a compiler for which test