Index: openacs-4/packages/acs-core-docs/www/unit-testing-guide/index.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/unit-testing-guide/index.adp,v diff -u -r1.1.2.1 -r1.1.2.2 --- openacs-4/packages/acs-core-docs/www/unit-testing-guide/index.adp 23 Sep 2015 18:37:48 -0000 1.1.2.1 +++ openacs-4/packages/acs-core-docs/www/unit-testing-guide/index.adp 9 Jun 2016 13:03:12 -0000 1.1.2.2 @@ -68,20 +68,20 @@

If you need to create a set of tests for a module, the first step is to create a directory tree beneath the module directory. The current convention is to put all .java files in a -"/java/src/com/arsdigita/acs/module name/test" directory. -The module name should be the ACS module name, but with all +"/java/src/com/arsdigita/acs/module name/test" directory. +The module name should be the ACS module name, but with all dashes removed and with appropriate capitilization. All .java files that you create that contain test cases must have the word Test in the filename. All of the classes you create should be in the -com.arsdigita.acs.module name.test package, and should +com.arsdigita.acs.module name.test package, and should import "com.dallaway.jsptest.*" and "junit.framework.*" (and optionally, if needed, com.arsdigita.acs.acsKernel.ACSCommon). Next, the public class needs to extend "TestCase", and provide new method definitions for "suite()" and the constructor. Typically, in the constructor, you should extract the system property "system.url" to determine which server to test against.


-Last updated - 2000-12-19 +Last updated - 2000-12-19
pmcneill\@arsdigita.com