(completed) Sakai 10 Release Candidate Testing
Sakai 10 Test Fest
Sakai 10 - RC02/RC03
Release Candidate testing is now active.
The job of QA testers is to break Sakai. We want to find as many bugs as possible so that they can get fixed before a community release.
RC02 server - Longsight QA server and Indiana QA server
https://sakaiproject.atlassian.net/browse/SAK-26335 - link new bugs you find to this issue.
Before you start!
Create a Jira account: https://jira.sakaiproject.org
Subscribe to the QA email group: http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
Jira Process
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 neal.caidin@apereo.org
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 neal.caidin@apereo.org .
Resources
QA Servers - Sakai 10 - Servers available for testing can be found here.
- This doc outlines a beginners guide to entering a JIRA ticket.
Test Plan Overview
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 sakai-qa@collab.sakaiproject.org or directly to Neal Caidin - Sakai Community Coordinator
http://www.screencast.com/t/6lZA8nDsHzj - Sakai documentation
http://www.screencast.com/t/3A3bdH8or09 - reporting a Jira
Intro to Functional Testing Webinar (link appears to be broken)
Creating a test user
Creating a test site
Adding participant to site