Index: openacs-4/packages/acs-core-docs/www/unit-testing-guide/index.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/unit-testing-guide/index.html,v diff -u -N -r1.1 -r1.2 --- openacs-4/packages/acs-core-docs/www/unit-testing-guide/index.html 13 Mar 2001 22:59:26 -0000 1.1 +++ openacs-4/packages/acs-core-docs/www/unit-testing-guide/index.html 7 Aug 2017 23:47:54 -0000 1.2 @@ -20,17 +20,17 @@
-Once Ant is working, you'll need to obtain copies of both +Once Ant is working, you'll need to obtain copies of both JUnit and HTTPUnit. JUnit is a framework to automate the running of unit tests, and HTTPUnit provides @@ -47,7 +47,7 @@
-You should now be ready to run the tests. Go to your server's "packages"
+You should now be ready to run the tests. Go to your server's "packages"
directory and type source ./paths.sh
to set up your classpath.
Now type ant
. Ant should find the toplevel build.xml file,
check that it can see JUnit, compile your java files, and finally call Ant on
@@ -60,7 +60,7 @@
Adding new test cases is meant to be as easy as possible. Simple create a
new function in the appropriate .java file, making sure that the function
-name begins with "test". I've adopted a naming convention where the function
+name begins with "test". I've adopted a naming convention where the function
name consists of the word "test", a short description of what the function
does (with words delimited by underscores), followed finally by the QAS
testcase ID, if such a testcase exists. If you need to test an area of the