Scheduled for May 1st, 2012
Testers are not required to dial in to the audio bridge. It's just an option for those who want to be able to ask questions and share information.
Day/Time: Tuesday, May 1st, 11am PT / Noon MT / 2-3 ET / 18:00 UCT
Phone number: (317) 278-7008 Access Code: 484896#
- Sakai Jira
- List of 2.9 Test Servers (the server recommended for testing is http://qa3-us.sakaiproject.org:8086/portal)
- Samigo 2.9 Test Scripts (a public Google Spreadsheet)
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 on a daily basis, so don't expect your test accounts, sites, and user data to be available for more than 24 hours.
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-instructor, leward-student, leward-TA) 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.
- 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 Samigo 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
Before you start testing, sign up for the task(s) 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.
All of the functional testing tasks are listed in the Google workbook named SamigoTests 2.9. Each worksheet (tab) contains one more sets of tasks as described below:
- Jira Verification - this is a list of bug fixes and enhancements that need to be verified. To sign up to verify one or more of these, add your name to the Tester Name column for the items you plan to test.
- Samigo Export/Import - regression test scripts that focus on importing and exporting assessments. Find the first empty column and fill out the requested information (Name, Date, Tag, Browser, OS) in Row 2.
- Samigo Question Pools - regression test scripts that focus on creating and manipulating question pools. Find the first empty column and fill out the requested information (Name, Date, Tag, Browser, OS) in Row 2.
- Samigo AssessAuthor - regression test scripts that focus on authoring assessments. Find the first empty column and fill out the requested information (Name, Date, Tag, Browser, OS) in Row 2.
- Samigo Delivery - regression test scripts that focus on authoring assessments. This set of tests is very long. Each major section has a light blue background. Sign up for one section at a time.
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.
Testing bug fixes and enhancements
- The Google doc contains a link to each Jira. Click the link to read the original description and all comments in the Jira so you have a thorough understanding of the problem or enhancement.
- For bugs, try to reproduce the problem in a previous version of Sakai so you can see exactly what the problem looks like. Then try to reproduce the problem in Sakai 2.9x. For enhancements, read the description of the enhancement and review any designs or specs that are attached to the Jira. Then experiment with the feature in 2.9 to make sure it behaves as intended. Be sure to exercise every widget and option.
- Document your results be filling out the other fields in the Google doc for the issue. Use the status column to indicate whether you were able to successfully verify the issue. Enter a "y" for success and and "n" for failure.
- If everything checks out, add a comment to the Jira indicating that you verified the issue. Provide information about the environment on which you verified (OS, Browser type and version, Server, and QA tag). If the problem does not appear to be fixed or the enhancement isn't working properly, re-open the Jira. If you discover a new problem as a result of your testing, create a new Jira after verifying that it has not already been reported.
- The regression test scripts are organized into four worksheets, each focusing on a different functional area. All four 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).
- 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.
The test scripts were adapted from scripts used for Indiana University's local instance of SAMiigo, which differs slightly from the community version. We've tried to eliminate all references to local customizations, but we may have missed some. If you encounter any errors in the scripts, please correct them. If you are unsure about whether the script is correct, you can ask during the conference call. At other times, send a message to firstname.lastname@example.org and email@example.com.
- 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 Samigo Issues and Reporting Samigo Bugs in Jira.