Prev | - |
by Joel Aufrecht
+ Automated Testing provides a framework for executing tests of all varieties and for storing and viewing the results. 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] 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] Because the current test package uses in-memory variables instead of database objects to track its tests, it is incompatible with the standard category package. It uses an internal, single-dimension category field. Should this eventually get extended, a more complete list of categories to implement could be: Because the current test package uses in-memory variables
+instead of database objects to track its tests, it is incompatible
+with the standard category package. It uses an internal,
+single-dimension category field. Should this eventually get
+extended, a more complete list of categories to implement could
+be: Forum Posting: tclwebtest with openacs-4/etc/install tests -- help getting started
+ Forum Posting: tclwebtest with openacs-4/etc/install tests -- help getting
+started
Forum Posting: Berlin bug bash proposal
+
-
Req # Status in 5.0 Priority for 5.1 (A=required, B=optional) Description
+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.
+Execute Tcl tests. Execute a
+sequence of Tcl code is executed and determine the correctness of
+the results.
1.1 partial Done
-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.)
+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 Done
-Execute tclwebtest scripts. A test can contain tclwebtest commands. If tclwebtest is not installed, those commands fail gracefully.
+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.)
+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 Done Done
-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.
+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.
- 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)
+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
-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.)
+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
-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 should be sharable by different OpenACS installations. It should be possible to import/export directly between running OpenACS sites. (We should look at what did and didn't work in acs-lang catalog files and work from there.)
+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
+should be sharable by different OpenACS installations. It should be
+possible to import/export directly between running OpenACS sites.
+(We should look at what did and didn't work in acs-lang catalog
+files and work from there.)
5 B
-Macro Recording. End users can create and run tests from the web interface without writing code.
-
- 6 A Notification subscriptions are available for "email me whenever this test fails" and "notify me whenever a test in this category fails"
+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.
+7 A The results of an automated test are optionally written to an
+xml file.
Testing Mode
+
+Testing Mode
Regression
Smoke
Stress
@@ -93,19 +133,16 @@
etc
-
+
+
@@ -119,13 +156,10 @@