Overview |
|---|
The Sakai 22 QA Hub is the home page for the Sakai 22 Quality Assurance effort. For questions please contact sakai-qa@apereo.org |
Testing |
|---|
The web page for all the testing servers can be found here: http://nightly2.sakaiproject.org/ The web page you want to use for testing Sakai 22 is: https://qa22-mysql.nightly.sakaiproject.org/ The above link for testing Sakai 22 can be found under 22.x test instances on the testing servers web page. To get quickly started with QA Testing, Here’s our Quick Guide |
Communication Channels |
|---|
Sakai QA listJoin 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: https://groups.google.com/a/apereo.org/forum/#!forum/sakai-qa Sakai QA Slack ChannelWe 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: https://apereo.slack.com/signup Otherwise, send an email to sakai-qa-planners@apereo.org 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: https://youtu.be/aB8PsAn97uo |
Meetings |
|---|
Weekly QA Planning CallsThe QA Planning Group meets every Wednesday from 5:30 pm - 6:30 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 by following this etherpad link: https://etherpad.nightly.sakaiproject.org/p/QA-Planning-Call. All are welcome! We meet in the QA Room in BigBlueButton: http://apereo.blindsidenetworks.net/apereo/ Subscribe to the meeting: https://calendar.google.com/calendar/u/2?cid=ZWRiOTZlNzFudG90ZjUzdjI2c2Q4ZGFubmdAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
|
Latest Version - Sakai 22.0 |
|---|
Sakai 22.0 was released April 14th, 2022. Below is the Sakai 22.0 release notes: |
QA Testing this week
With Sakai 22.0 being released this past week we want to focus on doing verification testing for the upcoming Sakai 21.3 release.
Sakai 21.x verification testing filter: https://sakaiproject.atlassian.net/issues/?filter=10060
The server we want to use for testing is the Sakai 21.x branch, https://qa21-mysql.nightly.sakaiproject.org/
This branch can be found here: http://nightly2.sakaiproject.org/
The Friday conference call (aka TestFest) will be held in the Sakai QA Room in BigBlueButton. BigBlueButton can be found by following this link: https://apereo.blindsidenetworks.net/apereo/ . In the drop down menu for rooms select Sakai QA Room. The password is apereo. Starting time is 10:00 AM EST.
Look forward to seeing everyone at Test Fest this week.
Server to use for testing
Unless otherwise stated, all testing is taking place on the Sakai 22 server (refreshed weekly on Mondays).
When testing notifications/email, you can check the Mail Catcher server to confirm sent messages - https://mail.nightly.sakaiproject.org/
Reporting Issues via Jira
JIRA Authoring 101 - An introduction to finding and reporting issues.
Watch a short video of how the reporting works.
JIRA Guidelines - basic workflow, and definitions for Issue Type and Status
Finally, To report an issue/create an Jira. You will need a Jira account. Please contact our wonderful team member Wilma Hodges .
Weekly Test Fests
Join our QA “Test Fests” every Friday 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 by following this etherpad link here: https://etherpad.nightly.sakaiproject.org/p/QA-Test-Fest. We begin our Test Fests in the QA Room in BigBlueButton (see left). Throughout the course of the Test Fest, we communicate using our new SakaiQA channel in Apereo’s Slack instance described under Communication Channels on this page.
*QA testing is informed by updates on the Core Team call and QA planning meetings which are held on Tuesday every week. Therefore, QA testing cycles usually run from Wednesday to Wednesday the following week. Longer QA cycles may be held during QA for major releases to accommodate more in-depth testing such as regression testing.
Useful Details / ResourcesTesting Resources - test files and content for Calendar, Gradebook, Lessons, Tests & Quzzies, CK Editor and general media/text files Some useful and quick guide for QA testers |
|---|