Versions Compared

Old Version 3

changes.mady.by.user Former user

Saved on

compared with

New Version 4

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 - QA06

QA06 testing is now active.

The job of QA testers is to break Sakai. We want to find as many bugs as possible so that they can get fixed before a community release.

  • QA07 server - Longsight QA server

  • Nightly trunk server - for verifying Jiras so that they can be merged into the Sakai 10 branch. Please note: the nightly server is refreshed every 4 hours starting at midnight Eastern daylight time, and all data will be lost. Please time your testing accordingly.

 

  • Test Fest Google doc - Start testing
  • Jira Legacy
    serverSakai
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId66e9c5b5-d22c-30a2-a9d4-703f4354570c
    keySAK-26229
    - link new bugs you find to this issue.

 

Note
titleQA meeting
QA check-in - TBD

 

 

 

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-qa06 Test Plan

Summary
Main focus is to try and break Sakai.
You can also try and verify fixed Jiras.
Tabs on the Google doc:

Need Testing to Merge - bugs fixed and we need them verified before we merge them in to the Sakai 10 branch. Verify Jiras on trunk.sakaiqa.org  

Blockers merged need testing - these are blocker bugs that were fixed before we cut the Sakai 10 branch, so they never had been verified. Preferably verify Jiras on Longsight QA server and Indiana QA Server or optionally trunk.sakaiqa.org (should be okay in most cases).

JIRA filter for "Need Testing to Merge" - https://jira.sakaiproject.org/browse/SAK-25884?filter=14328

Google Doc - Test Fest Google doc

 Email questions to the Sakai QA list or the Sakai Coordinator (aka Neal).

 

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

Searching for Jiras using Google