Index: openacs-4/packages/acs-core-docs/www/automated-testing-best-practices.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/automated-testing-best-practices.html,v diff -u -r1.1.2.6 -r1.1.2.7 --- openacs-4/packages/acs-core-docs/www/automated-testing-best-practices.html 18 Dec 2003 10:04:26 -0000 1.1.2.6 +++ openacs-4/packages/acs-core-docs/www/automated-testing-best-practices.html 11 Jan 2004 12:45:45 -0000 1.1.2.7 @@ -1,7 +1,7 @@ -Automated Testing

Automated Testing

By Jeff Davis

+Automated Testing

Automated Testing

By Jeff Davis


OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff. -

Best practices in writing OpenACS automated tests

  • Special characters in Tcl.� +

Best practices in writing OpenACS automated tests

  • Special characters in Tcl.� Try strings starting with a -Bad and strings containing [BAD], {, \077, and $Bad. For user input, [BAD] should never be evaluated, \077 should not be turned into a ? and $Bad should not be interpolated. The string -Bad [BAD] \077 { $Bad should be valid user input, should pass through the system unaltered, and if it isn't that's a bug.

  • Quoting issues.�Put some html in plain text fields and make sure the result is properly quoted anywhere it shows up (I use "<b>bold</b>"