Child pages
  • Sakai 10.3 Smoke 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.3 Testing Overview

More QA volunteers would be helpful.  Please email sakaicoordinator@apereo.org .

We are performing smoke testing and trying to break Sakai during our current testing. Until RC01 is available, we will be using the Sakai 10.x nightly server, which is refreshed daily. We are not allowing any more merges into Sakai 10.x as of December 5, 2014 and only blocker-level bugs which are found and fixed during testing will be included.

In this phase there is NO JIRA testing. It is ONLY testing 10.x (and 10.3-RC01 when it is built).

Assignments - 35
Samigo Test and Quizzes - 17
Gradebook - 7
Site Info - 6  (mostly groups)
Content - 4

and CK Editor was updated to a new version.

Smoke Testing needs
Significant testing has been done in Assignments, Samigo, Gradebook, Groups, WebDav and a little in Lessons. More testing could be used in all those areas. And a good workout of the CK Editor in various browsers would be helpful.

Testing fixed issues

All issues that were merged into 10.x, had been tested in trunk before merging. Re-testing in the 10.x branch is another great way to prevent regressions and ensure the functionality is working as intended. See the list of 10.3 fixes. Use the label "10xtested" to indicate a JIRA you have tested in the 10.x branch.

Please open new Jiras and relate to the parent 10.3 Jira - SAK-28093 - Getting issue details... STATUS

Thanks!

QA meeting

QA check-in (or real time Test Fest) - 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.3 Testing Details

Relate Jiras to the parent ticket - SAK-28093 - Getting issue details... STATUS

Testing server - Sakai 10.x nightly server

Source code changes for Sakai 10.3 - Sakai 10.3 source code changes

10.3 fixes - https://jira.sakaiproject.org/issues/?filter=15016

If you find a bug

If you find a bug in Sakai 10, please test to see if the issue exists on 10.x on server - Sakai nightly 10.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