Child pages
  • Sakai 10 QA02 Testing
Skip to end of metadata
Go to start of metadata

Sakai 10 qa1 Testing corresponds to the first round of QA testing for Sakai 10

Sakai 10 Test Fest

Sakai 10 - QA01/QA02

QA01/QA02 testing continues, through the end of January..


QA meeting

QA check-in - Tuesday, January 21, 2014 at 10 am Eastern, 7 am Pacific, 3 pm GMT on Adobe Connect .




Before you start!

Create a Jira account:

Subscribe to the QA email group:

Jira Process

  1. Sakai Jira Guidelines
  2. Everyone with a Jira account can create tickets, sub-tickets, search the system and add comments. Anybody can make a Jira account for him/herself. Others have additional permissions to update the fields on the ticket to reflect current status. If you think you need this level of access contact
  3. Updating a ticket with the "Tested" button - to verify a ticket requires clicking on the "Tested" button. You must be logged in to Jira and part of the Jira QA group. If you wish to be added to this group contact . 




Test Plan Overview

Sakai 10-qa02 Test Plan

This is essentially a continuation of QA01, which is why we are using the same Google doc, but a different JIRA for reporting. We still have more tools to "touch" (i.e. do at least some rudimentary testing), so that every tool gets at least a basic workout, and we want to verify as many JIRA issues which have been merged into Sakai 10 already. The spreadsheet is organized by Tool with an area for Regression testing and an area for JIRA testing on the same sheet. There is a also a sheet showing bugs fixed in QA01, which are ready to be tested.

In many cases, you will see "DIY" testing in the Regression area. DIY means do-it-yourself. Test a tool with which you are familiar. Try to break it! Open a JIRA for each issue you find. Add the issue as a link to SAK-25571 - Getting issue details... STATUS , which we will use to track the issues from this round of QA testing and triage them. If you can create a list of features you have tested within a tool, please consider sharing with the Sakai Community Coordinator, who can clean up your list, if necessary, and make available to the community for future rounds of testing.


If you find a bug

If you find a bug in Sakai 10, please test to see if the issue exists on 2.9.x on server - Sakai nightly 2.9.x . This will help determine if it is a regression.

To Get Your QA questions answered

To get your questions about QA testing answered, please email the QA group at or directly to Neal Caidin - Sakai Community Coordinator