Acceptance Test

for the Arsdigita Community System by Tracy Adams
Use this to test an ACS installation. Going through these steps is also a good way to learn the major features of Arsdigita Community System administration.


You should ensure the database has been properly configured and that your AOLserver installation will actually start.
Suggested method:


You should test basic registration and the login process.
Suggested method:

User Administration

You should test adding a user, searching for users, modifying user data, banning or deleting a user, and spamming a class of users.
Suggested method:

Bboard System

You should test setting up a bboard, posting a message, alerts, and searching.
Suggested method:

Classified Ads

You should test setting up a domain, posting/editing and ad, alerts, hot auctions and searching.
Suggested Method:


You should test adding new downloads, upload versions of existing downloads, adding rules to all versions/specific version of a download, edit/remove download data, download a file, view download history.
Suggested Method:

User searchers

The searches you made in the bboard and classified ads should have been logged. View the user searches section in the admin pages to verify.


You should test story posting, story approval, and story editing (for both site-wide and group scope). You can also test the interface into the general comments module.
Suggested Method:


You should test adding an event, approving events, and adding comments.
Suggested Method:


Neighbor to Neighbor

You should test creating a domain and subcategory, adding and approving a posting, adding and adding and approving a comment, and searching. Suggested Method:

Stolen equipment registry

You should test adding and entry, adding a comment, and searching.
Suggested method:

HTML Comments and Related Links

You should test syncing the html pages with the database, adding/editing comments, adding/editing related links.
Suggested method:


You should test that clickthroughs are logging.
Suggested Method:

Ad Server

You should test that you can insert and view ads.
Suggested Method:

Contest System

You should test setting up a contest, contest entry, modifying contest parameters, and voting.
Suggested method:

Ticket Tracker

You should test adding users, creating a project, and creating an issue.
Suggested path:





Pull-Down Menus

Address Book

You should test adding, editing, viewing and searching for a contact.
Suggested path:


You should test searching and browsing the directory.
Suggested path:


You should test definition entry, editing, approval, and deletion.
Suggested Method:

General Links

You should test link entry, rating, editing, approval, and deletion.
Suggested Method:


You should test poll entry, editing, voting, and reporting.
Suggested Method:

User groups

You should test links to sections, group membership and group spamming.
Suggested Method:

General Permissions

Run the automated acceptance test. This tests all PL/SQL functions against the data model.


You should test adding, viewing, editing, and deleting a press item:



You should make sure that you can create an event, register for it, and review registrations.
Suggested method:

Template System

Go to a number of pages under /ecommerce/ and make sure they get displayed with uniform style, e.g.

   -> product-search
   -> gift-certificate-order-3
       -> gift-certificate-order-4
(The style is defined in /web/yourservername/tcl/ecommerce-styles).

Note: this is the old template system, documented in style; the new one by Karl Goldstein is not included in the ACS.

Categorization and User Profiling

You should be able to add categories, define their positions in category hierarchy and, as registered user, choose content categories you're interested in.


Stick this into a file and then access it with your browser:
set legend [list "1997" "1998" "1999" "2000"]

set subcategory_category_and_value_list [list [list "Dog" "Favorite Animal" [list "45" "47" "40" "45"]] \
                [list "Cat" "Favorite Animal" [list "20" "21" "19" "21"]] \
                [list "Other" "Favorite Animal" [list "35" "32" "41" "34"]] \
		[list "Pizza" "Favorite Food" [list "34" "33" "35" "35"]] \
		[list "Chocolate" "Favorite Food" [list "24" "25" "24" "25"]] \
		[list "Other" "Favorite Food" [list "42" "42" "41" "40"]]]

ns_return 200 text/html "<font face=arial size=+2>Madrona Elementary School Annual Poll Results</font>
[gr_sideways_bar_chart -legend $legend $subcategory_category_and_value_list]
It should produce a lovely four-color bar chart!


After you have completed the setup tasks in Technical Details of the Ecommerce Module, here are some good tests of the things most likely to be broken: Once all this is working, you can further test your system:

Display Module

Test cascaded style sheet settings and uploading of a logo

General Comments

Test tcl procedures used for adding comments to pages and test general comments admin pages


Make sure that help links work and that appropriate .help files are used

Content Sections

Test content section admin pages

New modules

Systematically go through each option making sure:


Suggested Method:

Data Pipeline

Data Pipeline will be fully exercised by the Intranet module.

Simple Survey

You should test creating a new survey, editing a survey, enabling a survey, responding to a survey and viewing responses.



Referer Module

Member Value Module

Education Module


Robot Detection

In order to test the Robot Detection package, we need to be able to request URLs from the site with a User-Agent that is listed in the robots table and see for ourselves that the results are as expected.

The simplest approach to testing this is to add a FilterPattern into the [ns/server/yourservername/acs/robot-detection] section of the parameters file and to add a record into robots that matches a web browser program and use that browser to access the site. The following SQL works for Microsoft Internet Explorer 4.01 on Windows NT:

insert into robots(robot_id, robot_name, robot_details_url, robot_useragent)
values('msie4', 'Microsoft Internet Explorer 4.0 (for testing purposes only)',
'', 'Mozilla/4.0 (compatible; MSIE 4.01; Windows NT)');
Just be sure to delete this row when you go into production!