Versions Compared

Old Version 23

changes.mady.by.user Former user

Saved on

compared with

New Version 24

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Sakai 10 qa1 Testing corresponds to the first round of QA testing for Sakai 10

Info
titleSakai 10 Test Fest

Sakai 10 - QA01

QA01 testing officially opens Tuesday, December 17, 2013. Estimated to run through mid to late January.

QA check-in - Tuesday, December 24, 2013 at 10 am Eastern, 7 am Pacific, 3 pm GMT on Adobe Connect (thanks to Indiana for use of the Connect room).

Adobe Connect (log in as guest)
http://connect.iu.edu/s3room1

 

Info
Known blocker bug - Portfolio system cannot be used with this iteration of QA. However it will be a blocker for future iterations of QA
Jira Legacy
serverSakai
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId66e9c5b5-d22c-30a2-a9d4-703f4354570c
keySAK-23775
Info
titleBefore you start!

Create a Jira account: https://jira.sakaiproject.org

Subscribe to the QA email group: http://collab.sakaiproject.org/mailman/listinfo/sakai-qa

Jira Process

  1. Sakai Jira Guidelines
  2. Everyone with a Jira account can create tickets, sub-tickets, search the system and add comments. Anybody can make a Jira account for him/herself. Others have additional permissions to update the fields on the ticket to reflect current status. If you think you need this level of access contact neal.caidin@apereo.org
  3. Updating a ticket with the "Tested" button - to verify a ticket requires clicking on the "Tested" button. You must be logged in to Jira and part of the Jira QA group. If you wish to be added to this group contact neal.caidin@apereo.org . 

Resources

 

 

Info
titleTest Plan Overview
Note

Sakai 10 Test Plan

We want to touch as many tools as possible, 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.

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
serverSakai
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId66e9c5b5-d22c-30a2-a9d4-703f4354570c
keySAK-25466
, 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.

 

Info
titleIf you find a bug

If you find a bug in Sakai 10, please test to see if the issue exists on 2.9.x on server - Sakai nightly 2.9.x . This will help determine if it is a regression.

Tip
titleTo Get Your QA questions answered

To get your questions about QA testing answered, please email the QA group at sakai-qa@collab.sakaiproject.org or directly to Neal Caidin - Sakai Community Coordinator

Panel
titleHelpful Videos
Note

http://www.screencast.com/t/6lZA8nDsHzj   - Sakai documentation

 

Intro to Functional Testing Webinar (link appears to be broken)
Creating a test user
Creating a test site
Adding participant to site