| Next |
Table of Contents
Table of Contents
+
Automated Testing is part of acs-core, and therefore should already be installed in any OpenACS system. Individual automated tests are stored within each package in package/tcl/test. +
Automated Testing is part of acs-core, and therefore should already be installed in any OpenACS system. Individual automated tests are stored within each package in package/tcl/test.
Automated Testing provides a framework for executing tests of all varieties and for storing and viewing the results.
| Req # | Status in 5.0 | Priority for 5.1 (A=required, B=optional) | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Done | Done | Execute TCL tests. Execute a sequence of TCL code is executed and determine the correctness of the results. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 1.1 | partial | A | Execute HTTP tests. Execute tests that can interact with a the webserver via the external, HTTP interface, including retrieving pages, following links, and submitting forms. (This is partially done in the sense that we can make http calls from tcl api, but there is no framework for doing anything complicated.) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 1.1.1 | � | A | Execute tclwebtest scripts. A test can contain tclwebtest commands. If tclwebtest is not installed, those commands fail gracefully. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 1.1.1.1 | partial | A | tclwebtest is easy to install. Tclwebtest installation is fully documented and can be installed with less than five steps. (Install is documented in 5.0, but there's a can't-find-config error; also, some new work in tclwebtest HEAD needs to packaged in a new tarball release.) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 2 | � | A | Tests have categories. Individual tests can be marked as belonging to zero, one, or many of these categories. The UI provides for running only tests in selected categories, and for viewing only results of tests in selected categories.
+ Automated Testing provides a framework for executing tests of all varieties and for storing and viewing the results.
1) UI to turn on macro mode. 2) basic recording: when you fill out a form while macro mode is on, the submit is caught and displayed as tclwebtest code, and then executed. 3) UI for creating aa_true tests automatically, based on the content of the page. (For example, a form that says "the returned page must contain [ type regexp here] that spits out aa_true "test X" [string regexp blah blah] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 6 | � | A | Notification subscriptions are available for "email me whenever this test fails" and "notify me whenever a test in this category fails" | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 7 | � | A | The results of an automated test are optionally written to an xml file. |
Forum Posting: tclwebtest with openacs-4/etc/install tests -- help getting started
Forum Posting: Berlin bug bash proposal
