Joel
@@ -41,7 +41,7 @@
make http calls from tcl api, but there is no framework for doing
anything complicated.)
-| 1.1.1 | Â | Done |
+ | 1.1.1 | | Done |
Execute tclwebtest scripts. A test
can contain tclwebtest commands. If tclwebtest is not installed,
those commands fail gracefully. |
@@ -60,19 +60,19 @@
categories, and for viewing only results of tests in selected
categories.
-| 2.1 | Â | A | Each test can be associated with a single OpenACS.org bug (ie,
+ | 2.1 | | A | Each test can be associated with a single OpenACS.org bug (ie,
store bug id as in integer, or store full url so that this can
point to other bugs) |
-| 3 | Â | B |
+ | 3 | | B |
Tests can be ordered lists of other
tests. minimal: verify that a test proc can call other test
procs. Better: A test can be created within the GUI by selecting
other tests. This test is stored in the database and can be
exported. (This is related to a bigger issue of storing test
scripts in some format other than tcl procs.) |
-| 4 | Â | C |
+ | 4 | | C |
Test scripts can be imported and
exported. It should be possible to import a test into the
database from a file, and to export it to a file. These files
@@ -81,7 +81,7 @@
(We should look at what did and didn't work in acs-lang catalog
files and work from there.) |
-| 5 | Â | B |
+ | 5 | | B |
Macro Recording. End users can
create and run tests from the web interface without writing code.
1) UI to turn on macro mode. 2) basic recording: when you fill out a form while macro mode is
@@ -92,11 +92,11 @@
X" [string regexp blah blah]
|
-| 6 | Â | A | Notification subscriptions are available for "email me whenever
+ | 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
+ | 7 | | A | The results of an automated test are optionally written to an
xml file. |
@@ -156,14 +156,11 @@