From 3f52e01c9a9e8c792609dcf01342d903272c1f14 Mon Sep 17 00:00:00 2001
From: bangerth
Most of our tests are built in dedicated directories, i.e. work on copies
of deal.II that we don't usually use to work on every day. We do this,
- because we want to see if the version in the CVS repository can be
+ because we want to see if the version in the subversion repository can be
compiled, not the version that we have made changes in.
- To run the testsuite, you first need CVS access to our source
+ To run the testsuite, you first need subversion access to our source
repository. If you have that, do the following steps:
Tests are a way to make sure everything keeps working. If they
aren't automated, they are no good. We are therefore very
- interested in getting new tests. If you have CVS write access
+ interested in getting new tests. If you have subversion write access
already, you have to add the new test and the expected output
file, and to commit them together with the changed Makefile, like
so:
Running it
cd /path/to/deal.II
- cvs checkout tests
+ subversion checkout tests
This should generate a tests/
directory parallel to
the base/
, lac/
, etc directories. Then
@@ -169,7 +169,7 @@
Once you have done this, you may simply type
make
. This runs all the tests there are, but stops at
the first one that fails to either execute properly or for which
- the output does not match the expected output found in the CVS
+ the output does not match the expected output found in the subversion
archive. This is helpful if you want to figure out if any test is
failing at all. Typical output looks like this:
@@ -278,7 +278,7 @@
test's name.) If this produces errors or triggers assertions, then you will
want to use a debugger on the executable to figure out what happens. On
the other hand, if you are sure that this also worked, you will
- want to compare the output with the stored output from CVS:
+ want to compare the output with the stored output from subversion:
make hierarchical/OK
@@ -521,18 +521,18 @@ testname/cmp/generic
- cvs add bits/my_new_test.cc
- cvs add bits/my_new_test
- cvs add bits/my_new_test/cmp
- cvs add bits/my_new_test/cmp/generic
- cvs commit -m "New test" bits/my_new_test* bits/Makefile
+ subversion add bits/my_new_test.cc
+ subversion add bits/my_new_test
+ subversion add bits/my_new_test/cmp
+ subversion add bits/my_new_test/cmp/generic
+ subversion commit -m "New test" bits/my_new_test* bits/Makefile
- If you don't have CVS write access, talk to us on the mailing
+ 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
contribute!
diff --git a/deal.II/doc/development/toc.html b/deal.II/doc/development/toc.html
index a6382c20fd..1526b67c8e 100644
--- a/deal.II/doc/development/toc.html
+++ b/deal.II/doc/development/toc.html
@@ -5,7 +5,7 @@
-This is the list of changes between the main cvs branch and the +This is the list of changes between the main subversion branch and the anisotropic branch of deal.II library. It is subdivided into changes made to the three sub-libraries base, lac, and /dev/null) ; then \ echo "Checking `pwd`" ; \ -- 2.39.5