Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


The Sakai 19 QA Hub is the home page for the Sakai 19 Quality Assurance effort.

For questions please contact

Communication Channels

Sakai QA list

Join the Sakai QA list (sakai-qa@ to keep up to date on all things QA in Sakai. Anyone can join the group here:!forum/sakai-qa

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  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:


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 19 QA Running Meeting Notes google doc. All are welcome! We meet in the QA Room in BigBlueButton: 
QA Room
password: apereo

QA Testing this week  -




19/2019 -





This week for QA, we are focusing on testing medium-priority tools.  Most of these tools will use a more light-weight testing approach (smoke testing) however we are regression testing LTI.  If you have experience with LTI, please take time to test this functionality in Sakai even if others have signed up to test the tool.If you find problems in a tool that you are smoke testing, please make a comment in the Comments column on the spreadsheet so we determine if more extensive testing is required. All testing will take place on the RC01 server here - use our new Sakai 19 RC01 QA spreadsheet for testing sign up and links to scripts:Sakai 19 RC02 here -  All tools except Rubrics, Gradebook, and Assignments should be lightly tested.  Rubrics, Gradebook and Assignments should be given a more rigorous test but not full regression testing.  A good rule of thumb is that a quick test should take about 20 minutes, and a more thorough test should take about an hour.  If you find problems, please create a JIRA using the instructions below.  Our goal with QA is to determine if 19 is ready for a release later this week.
The new signup sheet for testing RC02 is here -

Reporting New Issues via Jira

Steps for testing

  • All high-priority tools have scripts that can be found in the testing script column.  Use this for testing.
  • Test on multiple browsers.  Mobile is great if you can test there, too.
  • If you find new bugs, please create a new Jira and add that to your testing results (see Reporting Issues below)
  •  For reference, all related JIRAs for a specific tool are listed in the Jira column.
    Server to use for testing
    Unless otherwise stated, all testing is taking place on the Sakai 19 RC01 RC02 QA server - (refreshed weekly on Mondays)

    When testing notifications/email, you can check the Mail Catcher server to confirm sent messages -
    Reporting Issues

    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 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 sessions 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 / Resources

    Video: How to create a Jira

    Sakai QA bug fix workflow.pdf

    Signup and scripts for testing Sakai 19 RC01

    Testing Resources - test files and content for Calendar, Gradebook, Lessons, Tests & Quzzies, CK Editor and general media/text files