All bugs can be found on Launchpad. If you wish to read the bug description, please visit https://bugs.launchpad.net/systers/+bug/<bug number>, exchanging <bug number> for the bug number listed below for the bug you are interested in.

• Bug #345510 specific test instructions: check the archives for a dlist. At the bottom of each message there should be line saying: “To contribute to this conversation, send mail to <listname+threadname at domain>” where the listname etc. is exchanged for the real listname

• Bug #344063 test instructions: click on the link in one of the emails you get from a dlist allowing you to unsubscribe from a conversation. It should take you to a page with a button to unsubsribe from a conversation. You first need to provide your email and password and then click on the unsubscription button. A notification at the top of the page should tell you that you have been unsubscribed from the conversation and offer you a link to subscribe again. Feel free to subscribe again but before that, check the psql db in the table 'override'. It should say that the subscriber id corresponding to the email address just unsubscribed (id can be found in table 'subscriber') has preference '0' set for the thread number you just unsubscribed from (thread number can be found in table 'thread'). After subscribing again, the preference should be set to '1'. The table 'override' is empty until a change has been done at least once.

• Bug #391549 test instructions: http://launchpadlibrarian.net/30152030/test_bug391549.txt

• Bug #393415, #316261, partly #365164 test instructions: Check that when creating a list you can choose to enable the essay and if so create four new lists: one dlist w/ essay and one w/o, one non dlist w/ essay and one w/o. While creating the dlists, try changing the text for the questions (using markdown syntax). Enter the listinfo pages for the new lists. The ones without essay shouldn't have one and the ones with should have the text you specified (the standard Systers questions are the default questions when creating the list).

• Bug #398823 test instructions: try sending a message to a non dlist (as a subscriber) and see that it gets through to the list, in digest and that it ends up in the archives.

• Bug #296180 test instructions: let a subscriber try to subscribe to a list without entering fullname (fullname required should be set when creating the list). The subscriber should get a message to enter a fullname before being able to proceed. Now let the subscriber try to subscribe without entering an essay (essay enabled must be set when creating the list). The subscriber should get a message asking to answer the questions before being allowed to continue.

• Bug #365164 - partly (no separate bug was filed for this), test instructions: edit mm_cfg.py and set debug_mode to 'True'. Make a change on a list that affects the psql db, for instance subscribe a new user. Check the info log, it should contain new data about the subscription. Set the debug_mode to 'False' and again make a change affecting the psql db. Check the info log, nothing new should have been written to the log.

• Bug #365167 test instructions: create two new lists and for one of them, set fullname required to 'yes' and for the other list set it to 'no'. Visit the subscription pages of the lists, the one with fullname required should have a field for filling in the name and the list w/o fullname required should not. Subscribe users to the both lists. When confirming the subscription online, the one w/ fullname should write the name out at the page with the subscription button and the other list should not write out your fullname. In the database storing information about the users, the fullname will be set to 'None' for the list not requiring fullname.

• Bug #396108 test instructions: use the bash and type

 cd /usr/local/mailman
bin/rmlist -a <listname>

Check http://abiwt.org/mailman/listinfo to see that the list was removed. If it was a dlist, check the psql database to see that the list was removed from there as well. For a non dlist there should be an error message in the error log saying that you tried to delete a database that wasn't there but if it was a non dlist this is ok. If you notice that the deletion seems to get stuck, it has probably a hard time deleting the psql db and an error message will be written to the logs. Please check the error log, should this be the case.

• Bug #406937 test instructions: let a subscriber to a list enter an “other incoming email address” on the options page. Try changing the subscribers email address. Enter the “new” options page for this subscriber - the other incoming email address should still be there.

• Bug #402121 test instructions: when creating a new list, choose to enable the essay and try to enter formated text not in markdown syntax (not just plain text, try entering for instance HTML or Java Script). When trying to create the list, you should get an error message asking you to only enter markdown syntax. Doing so, create the list and take a look at the listinfo page. The questions for the essay should look like nicly formated HTML text corresponding to the syntax you wrote.

• Bug #360890 test instructions: in the admin interface of a dlist and a non dlist, set reply-to go to the list instead of to the poster. Send messages to the lists. Try to respond to them and check that the reply-to address for the dlist is written on the format listname+thread@domain and the the reply-to address for the non dlist is written on the format listname@domain.

• Bug #410185 test instructions: http://launchpadlibrarian.net/30110547/test_bug410185.txt

• Bug #413250 test instructions: try to change Mail delivery status from enabled to disabled on a non dlist. It should view and accept the changes.

• Bug #413246 test instructions: run the script migrate_old_lists (located in the bin folder) and afterwards try to view the options page and listinfo page for “old lists”

• Changes to GUI test instructions for Robin: enter the page for creating a new list. Try clicking the links on the page and check that the instructions look ok.