Debugging and Automated Testing

Prev	Chapter�7.�Development Tutorial	Next

Important

This section is a work in progress.

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

Debugging

Developer Support.�The Developer Support package adds several goodies: debug +

Debugging

Developer Support.�The Developer Support package adds several goodies: debug information for every page; the ability to log comments to the page instead of the error log, and fast user switching so that you can test pages as anonymous and as dummy users without logging @@ -23,17 +23,17 @@ ?�searches�backward�
/�searches�forward.�
��

Manual testing

Make a list of basic tests to make sure it works

Test Num

Action

Expected Result

001

Browse to the index page while not logged in and +

Manual testing

Make a list of basic tests to make sure it works

Test Num	Action	Expected Result
001	Browse to the index page while not logged in and while one or more notes exist.	No edit or delete or add links should appear.
002	Browse to the index page while logged in. An Edit link should appear. Click on it. Fill out the form and click Submit.	The text added in the form should be visible on the index page.

Other things to test: try to delete someone else's note. Try to delete your own note. Edit your own note. - Search for a note.

Write automated tests

by Simon Carstensen

+ Search for a note.

Write automated tests

by Simon Carstensen

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

- + It seems to me that a lot of people have been asking for some guidelines on how to write automated tests. I've done several tests by now and have found the process to be