Versions Compared


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


Hints - Our primary tools are Jira, Google docs spreadsheets, and QA servers. Learning how to use Jira and what the fields represent is well worth the time.

Ways to Participate

  • Verify bugs that have been fixed.
  • Test new features.
  • Regression test existing features. 
  • Create Regression scripts (i.e. step-by-step instructions for performing regression tests.)
  • Release testing - testing alpha, beta, and release candidate versions before software is made generally available (GA aka production). 
  • Help maintain QA documentation in Confluence. Proof read. Make suggestions. Create short videos. 
  • Ask and answer questions on the email groups. 
  • QA team meetings. Attend the QA to bring up issues that need attention, to help plan for testing for releases, and more.


  • Expert QA knowledge needed - special skills are needed for some types of QA testing. 

Verifying bugs

We sometimes call this kind of testing Jira testing, because bugs and features are reported in Jira, and we can easily track the status of a Jira to know when it is ready for testing and to understand if it is targeted to be included in an upcoming release. 


Just like the Trunk is the latest release of the contributed software code base for Sakai CLE, the 2.9.x branch is the latest release of software which will make its way into CLE 2.9. Therefore, like Trunk, 2.9.x is constantly changing, though not as fast as Trunk. This is important. We have a branch manager for the 2.9.x release so that we can ask him/her to merge those fixes, but also so he can stop adding changes when we are ready to make a release. Test-Fix-"Merge-fixes-back-to-branch"-Test until we are happy with the quality of the software. Then it gets "tagged", which is a way of gluing all the bits of software that make up the release, so even as more changes are made to the "branch", the tag will never change, because it is a snapshot of the ever-changing-branch at a point in time. The tagged software gets bundled up and shipped (made available) to the community. 


Test New Features

Regression test existing features

Regression Testing with Scripts

Regression scripts

Release Testing

See the latest 2.9 Test Fest 

Special Needs

Maintain QA documentation

Ask and answer questions on email groups

QA team meetings

Expert QA knowledge

  • Accessibility Testing
  • Localization Testing (different languages)
  • Review of patches and fixes
  • Testing locally
  • Automated testing
  • Security testing (requires special permission)