Last updated May 331, 2017
Summary
Release candidate testing is to check for any regressions that may have been introduced by the improvements (mostly bug fixes) that were applied for the 11.4 release.
Main testing:
- We are re-testing as many Jiras as we can in the 11 branch. These Jiras have already been verified, but that was in Master, we now want to test on Sakai 11! The community has done a lot of testing on Sakai 11.4. Now is the time for a final "Sanity check", a run through of basic use cases for at least several tools.
Testing Instructions
The testing instructions are on a Google sheet.
Different field!
https://www.screencast.com/t/3HdyY6j7d84
But a few important notes (which also are on the sheet). The issues you are testing have already been tested on "master", the main sakai branch. But now we are testing them after merging to the Sakai 11 environment. Please look at the "11 status" setting in Jira. The status should say "Resolved" which means the issue has been merged into the 11 branch. After you verify the issue works on the 11 branch, and search for regressions as you test, please set the "11 status" field to "Verified" so that we know it has been tested specifically on the 11 branch. Include on your JIRA comments which server you tested on, and which browser and OS.
...
Normal Server !
The server to test on, for this iteration of RC01 is 11.x Maintenance Branch RC02 is Sakai 11.4-RC02 on MySql on http://nightly2.sakaiproject.org/. This not our norm, we usually set up a separate server for RC01 testing but not in this case. For RC02 we are likely to go back to our original way of choosing where to test, by creating an RC02 tag and putting up a server for it.
QA Tester Experience
This round of QA testing primarily is targeted at QA testers in the community who are experienced with Sakai and with the QA process. If you are new to QA testing on Sakai please send an email to sakaicoordinator@apereo.org and we will figure out something to assign you to do based on your experience level.
Target Date to Complete QA
Our to target date to complete RC01 testing is close-of-business, Thursday, WednesdayJune 1, May 172017.