The Sakai 12 QA Hub is the home page for the Sakai 12 QA effort.
We are testing new fixes on Master (next release version 19), to be merged back to the 12.x Maintenance Branch to prepare for our next maintenance release (12.4).
We are testing on the community server "Trunk (master) on MySql" . Master is the next version of Sakai (19) and where the process of applying all fixes to Sakai begins.
Useful Details / Resources
Google Drive resources for Sakai 12 - test scripts, sample content, and in-progress testing available here.
This Week for QA
Again for QA this week we will be testing new fixes in Master to be merged into the 12.x branch. Of the 20 JIRAs that need QA, most of them have the accessibility and qadevneeded labels. Please note we have 5 critical JIRAs with the Accessibility component, and 11 JIRAs that require QA by a developer. Test on your own, or join us Thursdays at 10 am in BBB QA Room for the weekly community Test Fest.
How to test:
- Look at the JIRAs that need testing:
- JIRAs that need DEV QA: https://jira.sakaiproject.org/issues/?filter=16697
- JIRAs that need Accessibility QA: https://jira.sakaiproject.org/issues/?filter=16698
- JIRAs for general community testing: SAK-40586, SAK-40459, SAK-40361, SAK-37978
- Select a JIRA you feel comfortable testing, assign it to you, and test it using the Test Plan in the JIRA.
- Once your JIRA is tested and the fix is confirmed, change the JIRA status field to VERIFIED.
- You're done. Thanks for testing!
Server to use for testing:
We are testing on the community server Trunk (master) on MySql . Master is the next version of Sakai (19) and where the process of applying all fixes to Sakai begins.
Next week 12.4 QA and Release Schedule
The goal is to release Sakai 12.4 by next Thursday, September 20. This will require QA testing Monday - Wednesday next week. There are 80 JIRAs that make up the 12.4 release with 5 being blockers.
JIRAs to be QAed for 12.4: https://jira.sakaiproject.org/issues/?filter=16712
Follow the testing steps 2 - 4 above for testing these JIRAs.
Server to use for testing 12.4:
Merges from Master will be suspended during testing next week on the 12.x branch where will we test the 12.4 JIRAs. All testing for this release will take place on the 12.x Maintenance Branch on MySql server.
The QA team will follow up next week about testing progress and any release updates for 12.4.
- JIRA Authoring 101 - An introduction to finding and reporting issues.
- Watch a short video of how the reporting works.
Weekly QA Planning Calls
The QA Planning Group meets every Tuesday from 2:00 pm - 3:00 pm, Eastern time . This group guides the overall direction of the Sakai QA effort, creates testing materials and processes, and participates in testing. Meetings agendas and notes can be found in our Sakai 12 QA Running Meeting Notes google doc . All are welcome! We meet in the QA Room in BigBlueButton:
Weekly Test Fests
Join our QA “Test Fests” every Thursday from 10am to 11 am, Eastern time! This is an opportunity to jump into testing Sakai with the support of the QA Team and other community members. You do not need to be an functional expert to get involved! Test Fest agendas and notes can be found in our Sakai QA Running Meeting Notes google doc . We begin our Test Fests in the QA Room in BigBlueButton (see above). Throughout the course of the Test Fest, we communicate using our new SakaiQA channel in Apereo’s Slack instance described below. The QA team will be available 30 minutes before Test Fest, at 9:30 am (EST), to help onboard those new to QA testing.
Sakai QA list
Sakai QA Slack Channel
We have a very active Sakai QA channel in Apereo’s Slack instance. We use this for communicating during Test Fests and asking QA questions to the group or to individuals anytime. If someone at your institution has already joined, then you can self join at:
Otherwise send an email to email@example.com to have your institution's domain added for self signup. For a quick overview of Slack (along with some helpful tips n’ tricks), see the following video: