Sakai 21 QA Hub

QA Testing this week 

This week for QA, we will continue working on updating the regression scripts in preparation for Sakai 22 testing. 

Here is a link to the master spreadsheet for the regression script update project for the first iteration that was done during Sakai 21 testing: 

https://bit.ly/RegressionScriptUpdateMasterSpreadsheet

We are now using this spreadsheet for the second iteration of updating the spreadsheets in preparation for Sakai 22 testing:

https://bit.ly/Master_Regression_Scripts_Update_Second_Iteration

For this project we will use the old regression script as a basis for the new regression scripts. We will omit old content that is no longer relevant. From there we will think about new test cases to test that people see among the schools that they work at. Overall goal is to make the regression scripts cover more testing space. Starting with the basic functionality to the everyday tasks for users. We will also be looking at JIRAs to see if there are some test cases we need to write into the regression script to test for. 

The server we want to use for testing is the Sakai 21 branch.

This branch can be found here: https://trunk-mysql.nightly.sakaiproject.org/portal/

Regression Script Update Project Progress:

• High Priority Tools:
  • 0 out of 32 high priority tools are marked Complete.
  • 12 out of 32 high priority tools are marked Work in progress.
  • 9 out of 32 high priority tools are marked Ready to Modify. 
• Medium Priority Tools:
  • 0 out of 18 medium priority tools are marked Complete.
  • 0 out of 18 medium priority tools are marked Work in progress.
  • 0 out of 18 medium priority tools are marked Ready to Modify.
• Low Priority Tools:
  • 0 out of 33 low priority tools are marked Complete.
  • 0 out of 33 low priority tools are marked Work in progress.
  • 0 out of 33 low priority tools are marked Ready to Modify.

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

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.