Child pages
  • (completed) Sakai 10 Release Candidate Testing
Skip to end of metadata
Go to start of metadata

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.

  • SAK-26335 - Getting issue details... STATUS - link new bugs you find to this issue.

 

QA meeting

QA check-in - Tuesday, 17 June, 2014 at 10 am Eastern / 2 pm GMT . Teleconference details tbd.

 

 

 

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

  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 neal.caidin@apereo.org
  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 neal.caidin@apereo.org . 

Resources

 

 

Test Plan Overview

Sakai 10.0 Release Candidate Test Plan

Summary

Main focus is a smoke test. To find any obvious problems.

Reporting

Each tester (or group of testers working together) will get their own Google document in which to put notes from their testing. Contact the Sakai Coordinator (Neal) for a link to your Google doc.

Smoke Testing

1) Creating a course site
2) Creating a project site
3) Creating at least one group. Try it in a course which had a manual roster added. Try it in a course with a provided (aka official roster) added. You can use instructor, instructor1 or instructor2 logins which have demo provided rosters. Try with Assignments and/or Tests and Quizzes for deploying activity to a group.
4) Releasing one Announcement to the whole site and one to just the group.
5) Creating an Assignment - checking that all the Assignment options are available. Adding the Assignment to the Schedule. Taking an assignment and grading it.
6) Creating a Test with the top 5 most popular question types. Taking the Test as a student role and grading it.
7) Creating a Syllabus, linking to an Assignment
8) Adding resources with Drag and Drop
9) Adding a Web Content link
10) Adding a page to the Wiki
11) Creating a Topic and posting twice in the Forums tool
12) Creating a Lesson with one conditional release item
13) Updating Profiles with two different accounts, connecting them, and creating a worksite for that ad hoc group
14) Emailing the class 

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