If you are new to QA testing for Sakai, there are some things that you learn about and do before the Test Fest begins:
Creating test accounts and sites on the Sakai QA servers
On the Sakai QA servers, each user creates his or her own test accounts and sites*. * Most of the QA servers are rebuilt periodically and the data is dropped, so don't expect your test accounts, sites, and user data to be available next time you log in.
To create a new account:
- Navigate to one of the Sakai 2.9 QA servers (the server recommended for testing is http://qa3-us.sakaiproject.org:8086/portal)
- Click New Account in the left navigation.
- Fill out the New Account form. Hint: It can be helpful to append a role name to the end of the username for each account you create (e.g., leward-coord, leward-participant, leward-evaluator, etc) and then assign these roles when you add users to sites. This makes it much easier to keep track of who's who when you've got multiple browsers and users logged in at the same time.
- Click Create Account. Your account will be created and you will be logged in automatically.
- If you want to create another account, click Logout and repeat steps 1-4.
To create a new site:
- Log in to the test server with one of your test accounts.
- Click Worksite Setup in the left navigation.
- Click New in the menu at the top of the page.
- Select a Site Type (e.g., project, course, portfolio) under Build Your Own and click Continue. Note: Due to a permissions setting in 2.9, only a Sakai administrator can create portfolio sites. However, on qa3 the permissions have been altered to allow regular users to create portfolio sites.
- Read the on-screen instructions and proceed through the site creation wizard. You'll be prompted to choose a name, select the tools you want to use, etc., and click Continue when you complete each page
- When you reach the last page in the Wizard, click Create Site.
It's important that functional testers be proficient with Jira, the system used to track bugs and enhancements for Sakai. Information about Sakai Jira and how to use it can be found in the the Sakai Jira Guidelines. If you are not familiar with Jira, please read this document before you begin testing and use it as a reference when working with Jira. We have also prepared some basic instructions for using Jira for testing OSP 2.9:
General Testing Tips
Read the page General Testing Tips for some great suggestions on testing any Web-based tool. This document was prepared for Sakai OAE but applies equally to tools in Sakai CLE.
Sign Up Before You Start Testing
The second tab in the OSP Scripts Google doc is a signup sheet. Before you start testing, sign up for the task(s) you plan to test by adding your name, tag, and server ID to row corresponding the item you plan to test. If someone else has already signed up for a specific task, look for a different one to do. That way we'll cover as much of the application as possible with a small group. When you have successfully completed the test script, put an "y" in the status column for that script. If you encounter one or more bugs, create a Jira, add a "n" to the status cell, and enter the Jira IDs into the Jiras and Comments column.
Some tools do not have scripts. Only sign up for those items if you are deeply familiar with the tool and feel confident that you can test it thoroughly without a test script.
It's often helpful to use several different browsers for testing, so you can be logged in under multiple usernames and roles at once. Firefox and Internet Explorer are the officially supported browsers for Sakai, so those should be your first choices. You may also use Chrome and Safari, but please do not create Jiras about bugs that are specific to unsupported browsers.
- Access the QA Scripts Google doc at: https://docs.google.com/spreadsheet/ccc?key=0AldPCURzarLgdFJUVm40QzlYMnhLZjRPNzluam0xZ1E&hl=en_US#gid=20
- The regression test scripts are organized into worksheets, each focusing on a different tool or functional area. All sheets contain a column for actions (what you are supposed to do), results (what you are supposed to see as a result of the action), and known issues (bugs related to the test case that have already been reported). Some of the scripts may be out of date. Please update them as you work through them. If you are unsure about the intended behavior of the tool or changes to the tool, contact Lynn Ward (email@example.com).
- Read the instructions at the top of the worksheet or the beginning of the test case before testing. Then complete each test step by step, following the instructions in the actions column. As you complete each step, enter a "y" into the worksheet if you were able to successfully complete the step or a "n" if you were not.
- If you discover a unreported bug related to a particular action, create a Jira and enter the JIra ID (e.g., SAM-1460) and enter the JIra ID in the Comments field for the test step on which the error occurred. For instructions on working with JIra, see Searching Jira for Existing OSP Issues and Reporting Samigo Bugs in JiraReporting OSP Bugs in Jira.