QA Testing

This is the first, unsupported release of our internal QA testing system. Note, it's not a real product yet, just a snapshot of some DTML and SQL methods. It will be a product eventually...

To make it go:

import the zexp into the Zope Root Folder (or somewhere else more convenient),
create a directory in Zope instance var/gadfly for the database,
set the correct name (the same as the directory you just created) in the test_db gadfly connection, and
use the db_create_sql method to create the database.

To start using the system, click on the list all tests link on the front page. It should be empty :) Now click on add a test. The fields there are:

Number: used to order and group tests. Components have 100-test blocks.
Component: some brief description of the component/sub-component being tested
Test name: a brief description of the actual test being performed
Description: the test itself
Expected outcome: the expected outcome of the test

... once you've got some tests in, click on the first test's name in the "list all tests". This will begin the test process. Perform the test and note any deviations from the expected outcome. If the outcome is correct, but some other issue comes up (say, with usability) then enter the issue in the design issue box. Now click "register and do next test" to move on.

Once outcomes are registered, you may follow the list all current issues link on the front page. Clicking on the test name brings us back to the test page with the current outcome at the top. A history of all outcomes will be displayed at the bottom. If the outcome has been fixed, then clicking on the [fixed] link on either the test page or the list all current issues will register it as fixed.

If you find that an outcome requires a comment, simply click the [edit] link and add a comment. Note that it's possible to "unfix" an outcome using this link.

Title	Type	Size	Modified	Status

QA Testing release 1.0	Software Release		2001-05-14	published
QA Testing release 1.0	News Item	1 K	2001-05-14	published