Sakai 10-qa02 Test PlanThis is essentially a continuation of QA01, which is why we are using the same Google doc, but a different JIRA for reporting. We still have more tools to "touch" (i.e. do at least some rudimentary testing), so that every tool gets at least a basic workout, and we want to verify as many JIRA issues which have been merged into Sakai 10 already. The spreadsheet is organized by Tool with an area for Regression testing and an area for JIRA testing on the same sheet. There is a also a sheet showing bugs fixed in QA01, which are ready to be tested. In many cases, you will see "DIY" testing in the Regression area. DIY means do-it-yourself. Test a tool with which you are familiar. Try to break it! Open a JIRA for each issue you find. Add the issue as a link to | Jira Legacy |
|---|
| server | SakaiSystem JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 66e9c5b597e0cfea-d22cfe72-30a2310f-a9d4a179-703f4354570c8363adfc350a |
|---|
| key | SAK-25571 |
|---|
|
, which we will use to track the issues from this round of QA testing and triage them. If you can create a list of features you have tested within a tool, please consider sharing with the Sakai Community Coordinator, who can clean up your list, if necessary, and make available to the community for future rounds of testing. |