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.
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.
For questions please contact firstname.lastname@example.org .
This Week for QA
This week for QA, we will be testing new fixes in Master to be merged into the 12.x branch. The status/timeline of a 12.4 maintenance release has not yet been decided, as many development efforts will be focused on the next major version, 19. DEVs, keep in mind the code freeze date for version 19 is August 31, 2018.
How to test:Look at the JIRAs that need testing:Priority testing needed for Blocker JIRA: https://jira.sakaiproject.org/browse/SAK-40375JIRAs that need DEV QA: https://jira.sakaiproject.org/issues/?filter=16697JIRAs that need Accessibility QA:
begin focusing on the upcoming Sakai 20 release for next year. With the upcoming Sakai 20 release we will be rewriting and updating the regression scripts for all tools. Last week we finished the smoke testing for Sakai 12.7. Therefore, we will release Sakai 12.7 at some point this week. No future releases beyond 12.7 have been mentioned.
JIRAs new features in Sakai 1916698
Steps for testing Community testing JIRAs: https://jira.sakaiproject.org/issues/?filter=16699Select 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!
- testing on these features are fine this week
- If you have problems with new features, comment on the JIRA or open a new JIRA
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.If you find a JIRA that you think is an accessibility issue but does not have the component Accessibility, please add that to the JIRA. If you find a JIRA without a test plan and it is not obvious how to test the issue, comment on the JIRA asking for a test plan from the reporter.
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
Join the Sakai QA list (sakai-qa@ apereo.org) to keep up to date on all things QA in Sakai. Anyone can join the group here:
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: