Overview |
---|
The Sakai 21 QA Hub is the home page for the Sakai 21 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 21 is: https://qa21-mysql.nightly.sakaiproject.org/ The above link for testing Sakai 21 can be found under 21.x test instances on the testing servers web page. |
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 Thursday from 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/ |
Latest Version - Sakai 21. |
---|
2 |
---|
Sakai 21. |
2 has |
200 improvements including
|
|
|
|
|
Other areas improved include:
|
Basic LTI
|
Feedback
|
Mail Sender
|
|
|
There was 1 security issue fixed in 21. |
2 (details will be sent to the Sakai Security Announcements list). |
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 forwant to continue testing for the Sakai 22.1 release.
The server we want to use for testing is the Sakai
2122 branch.
This branch can be found here: https://
trunkqa22-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.
org
- Sakai 22 needs verification filter:
- https://sakaiproject.atlassian.net/issues/?filter=10102
- 45 JIRAs currently
- Sakai 22 waiting verification to be merged to 22.
- test on master then it will be merged to 22 to test.
- https://sakaiproject.atlassian.net/issues/?filter=10103
- 61 JIRAs currently
Verifying master JIRAs if nothing left to verify.
- Any JIRA resolved.
- project = Sakai AND resolution = Fixed AND status = Resolved and resolutiondate >= -2w
- Anything fixed or resolved in the last 2 weeks.
- MASTER VERIFICATION only
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 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
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 |
---|