Difference between revisions of "MuDoc UAT"
| Line 2: | Line 2: | ||
Many thanks for your participation in the [http://selay1.srv.ualberta.ca:8080/MudocWeb/faces/Login.jsp MuDoc] UAT process. | Many thanks for your participation in the [http://selay1.srv.ualberta.ca:8080/MudocWeb/faces/Login.jsp 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 [[michaelf@ualberta.ca | send me an email]]. | ||
= Procedure = | = Procedure = | ||
Revision as of 12:40, 1 March 2007
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
- Review the MuDoc system; read MuDoc help and MuDoc FAQ.
- Register to create a MuDoc username, password, and profile.
- Login and try it out. Refer to MuDoc help for guidance.
- Report bugs using Bugzilla (ignore the warnings about expired certificate]. For a succinct guide to logging bugs, see Bugzilla user notes.
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.
