...
Welcome
- How are you ? Have you mastered the EZ QA process ?
What is this?
This is on level up from EZ Testing, the next "power up" to contribute to the QA effort. Here you will be testing fixes that have been made, but not applied yet to the 12 branch.
Workflow
- Developer fixes a bug on "master". Master is the main branch of Sakai development and is under constant improvement.
- Developer (or someone knowledgeable about Sakai) sets the field "12 status" = merge. There is a status flag for every branch "11 status", "10 status" , etc. NB: There is an overall "Status" field which is for the JIRA overall.
- JIRA is "Resolved/Fixed" with a fix version of "13.0 Tentative" . 13.0 is identical in meaning to "master" at this time (until we branch it in about a year, and master becomes 14.0).
- QA tester (you) , tests the fix on master, sets it to verified if it passes.
- If verified the branch manager merges the fix into the 12 branch. It will be in the 12.0 release!
Where to get help?
Email sakaicoordinator at apereo.org . There are more, and preferred options than this (see below). But if you get lost, feel free to reach out.
JIRA
Where to test
- Mostly on the Sakai 12 QA test server to begin testing.
- Sometimes on a Sakai 11 QA test server to compare the behaviorPlease test on "Trunk (master) on MySql"
How to test (click here)
What to test
Full list of issues - click here
Subset with label of "qaready"- click here
This means Neal had a chance to triage the issue and there is either a Test Plan or probably enough information in the description for testing. Jiras without this label means either they don't have a Test Plan or Neal hasn't had a chance to review them.
Additional Community and Support
...