From: bangerth Date: Thu, 4 Dec 2008 21:27:14 +0000 (+0000) Subject: Update X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=16cadc7050314ab2854920f3e31fcd5fa5d8621f;p=dealii-svn.git Update git-svn-id: https://svn.dealii.org/trunk@17842 0785d39b-7218-0410-832d-ea1e28bc413d --- diff --git a/deal.II/doc/development/testsuite.html b/deal.II/doc/development/testsuite.html index 2d23e4eda8..3fc7dc3f31 100644 --- a/deal.II/doc/development/testsuite.html +++ b/deal.II/doc/development/testsuite.html @@ -16,13 +16,16 @@

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 +

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 and with different (versions of) compilers, the regression tests are actually run and their output compared with previously stored. These two testsuites are described below.

+

The build tests

With our build tests, we check if deal.II can be compiled on @@ -116,6 +119,7 @@

+

The regression tests

@@ -369,17 +373,17 @@ int main () things behind the scenes that are helpful in this context). In above case, we only (nonsensically) write a zero to the output file. Most tests actually write computed data to the output file - to make sure that whatever we computed is what we got when the - test was written first. + to make sure that whatever we compute is what we got when the + test was first written.

There are a number of directories where you can put tests in. Extensive tests of individual classes or groups of classes have traditionally been into the base/, - lac/, deal.II/, fe/, or - multigrid/ directories, depending on where the - classes that are tested are located. + lac/, deal.II/, fe/, + hp/, or multigrid/ directories, depending on + where the classes that are tested are located.

@@ -388,7 +392,8 @@ int main () library, often only a single function. These tests go into the bits/ directory and often have names that are composed of the name of the class being tested and a two-digit - number (for example, dof_tools_11). + number (for example, dof_tools_11). There are also + directories for PETSc and Trilinos wrapper functionality.

@@ -531,6 +536,22 @@ testname/cmp/generic svn add bits/my_new_test/cmp/generic svn commit -m "New test" bits/my_new_test* bits/Makefile + In addition, you should do the following in order to avoid that the files + generated while running the testsuite show up in the output of svn + status commands: +
+      svn propset svn:ignore "obj.*
+        exe
+        output
+        status
+        OK" bits/my_new_test
+      svn commit -m "Ignore generated files." bits/my_new_test
+    
+ Note that the list of files given in quotes to the propset command extends + over several lines. +

+ +

If you don't have subversion write access, talk to us on the mailing list; writing testcases is a worthy and laudable task, and we would like to encourage it by giving people the opportunity to