MuDoc UAT

Greetings to MuDoc UAT (User Acceptance Testing) participants:

Many thanks for your participation in the MuDoc UAT process. Anyone can create a MuDoc account. However you cannot report bugs without a Bugzilla account. If you have already asked to become a tester, you should have received Bugzilla account information by email. If not please send me an email.

Procedure

1. Review the MuDoc system; I've created some online references: MuDoc help and MuDoc FAQ.
2. Register to create a MuDoc username, password, and profile.
3. Login and try it out. Refer to MuDoc help for guidance.
4. Report bugs using Bugzilla (ignore the warnings about expired certificate]. For a succinct guide to logging bugs, see Bugzilla user notes.

Suggestions

• You'll want to create several different users, probably at least three (one to submit, another to review, a third to edit), in order to test all of MuDoc's features, since peer review is a multi-role protocol. Otherwise your submissions will depend on someone else for approvals. It's best to take on all roles at once in order to test autonomously.
• I suggest that you keep track of these users by naming them appropriately.
• You may also want to log exactly what has been submitted and reviewed. Keeping these logs online (so you can review them while testing) is a good idea.
• If your work is being held up by lack of approval from a superior editor, please email me out of band.

Reference

• The formal testing process is described in the UAT plan, which you should at least skim before starting.
• An overview of MuDoc functionality is available in the MuDoc system description.
• MuDoc help provides detailed explanations of the user interface.
• MuDoc FAQ may also be useful (and feel free to add questions of your own here)
• Please refer to the MuDoc Functional Spec as a standard reference for what the system is supposed to do.

You can also email me with other questions.