Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 47 Next »

Overview

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

For questions please contact sakai-qa@apereo.org

Communication Channels

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: https://groups.google.com/a/apereo.org/forum/#!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: 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 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:

http://apereo.blindsidenetworks.net/apereo/ 
QA Room
password: apereo

QA Testing this week  - 2/12/2019 - 2/20/2019*


Sakai 19 RC01 is ready for testing!  This week for QA, we are focusing on testing high-priority tools.  Some of these tools, such as Assignments, Gradebook, Lessons, Tests & Quizzes, and Rubrics, require regression testing to confirm new bugs have not been introduced from previous issues that have been fixed. 

For all other high-priority tools, we are using a simplified testing strategy - smoke testing.  The scripts for smoke testing are much simpler and high-level.  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 - https://qa1-us.nightly.sakaiproject.org/portal

Please use our new Sakai 19 RC01 QA spreadsheet for testing sign up and links to scripts:

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 QA server - https://qa1-us.nightly.sakaiproject.org/portal (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

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. The QA team will be available 30 minutes before Test Fest, at 9:30 am (EST), to help onboard those new to QA testing

*QA testing is informed by updates on the Core Team call and QA planning sessions which are held on Tuesday every week.  Therefore, QA testing cycles 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

  • No labels