Index: openacs-4/packages/acs-automated-testing/www/doc/requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-automated-testing/www/doc/requirements.html,v diff -u -r1.2 -r1.3 --- openacs-4/packages/acs-automated-testing/www/doc/requirements.html 21 Jan 2004 18:26:58 -0000 1.2 +++ openacs-4/packages/acs-automated-testing/www/doc/requirements.html 29 Jan 2004 12:57:18 -0000 1.3 @@ -1,7 +1,7 @@ -Requirements
Prev

Requirements

by Joel Aufrecht


+Requirements
Alex logo
Prev

Requirements

by Joel Aufrecht

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

Introduction

Automated Testing provides a framework for executing tests of all varieties and for storing and viewing the results.

Functional Requirements

Req #Status in 5.0Priority for 5.1 (A=required, B=optional)Description
1DoneDoneExecute TCL tests. Execute a sequence of TCL code is executed and determine the correctness of the results.
1.1partialAExecute 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�AExecute tclwebtest scripts. A test can contain tclwebtest commands. If tclwebtest is not installed, those commands fail gracefully.
1.1.1.1partialAtclwebtest 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�ATests 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. +

Introduction

Automated Testing provides a framework for executing tests of all varieties and for storing and viewing the results.

Functional Requirements

Req #Status in 5.0Priority for 5.1 (A=required, B=optional)Description
1DoneDoneExecute TCL tests. Execute a sequence of TCL code is executed and determine the correctness of the results.
1.1partialAExecute 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�AExecute tclwebtest scripts. A test can contain tclwebtest commands. If tclwebtest is not installed, those commands fail gracefully.
1.1.1.1partialAtclwebtest 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�ATests 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. 
Testing Mode
   Regression
   Smoke
@@ -26,4 +26,4 @@
   5.0.0
   etc
2.1�AEach 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�BTests 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�CTest 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�BMacro 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 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�ANotification subscriptions are available for "email me whenever this test fails" and "notify me whenever a test in this category fails"

References

Revision History

Document Revision #Action Taken, NotesWhen?By Whom?
1Creation17 Jan 2004Joel Aufrecht
2Updated with notes from chat meeting21 Jan 2004Joel Aufrecht
Prev Home
Installation Up
docs@openacs.org
View comments on this page at openacs.org
+

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�ANotification subscriptions are available for "email me whenever this test fails" and "notify me whenever a test in this category fails"
7�AThe results of an automated test are optionally written to an xml file.

References

Revision History

Document Revision #Action Taken, NotesWhen?By Whom?
1Creation17 Jan 2004Joel Aufrecht
2Updated with notes from chat meeting21 Jan 2004Joel Aufrecht
Prev Home
Installation Up
docs@openacs.org
View comments on this page at openacs.org