[Deploying Sakai] Sakai 10-qa03 QA testing

Neal Caidin neal.caidin at apereo.org
Mon Feb 24 08:51:20 PST 2014

[announcements, production, sakai-user, pedagogy, i18n, accessibility, 
sakai-docs, sakai-dev, sakai-qa]

Dear Community,

We are at a major milestone for Sakai 10. QA03 represents code freeze 
and string freeze and the beginning of our major phase of testing to get 
to a release candidate [1]. Congratulations! We can use help testing at 
any point that you are available in the 1 - 1.5 months, approximately. 
The goal of QA testing is to break Sakai, and uncover as many bugs as 
you can find.

How can you help?
* Join the sakai-dev or the sakai-qa lists [2] - Most of the 
communication for the testing phase goes to the sakai-dev and sakai-qa 
lists. If you are not already a member of one of these lists, please 
join. sakai-qa gets less traffic and is therefore more appropriate if 
you are joining to help test.

* Get a Jira account - we ask our testers to report issues in Jira, our 
central bug reporting system for Sakai. If you are uncomfortable with 
Jira and wish to explore other arrangements, please email me at 
neal.caidin at apereo.org. Please make sure to link new bugs that you find 
to our parent Jira - https://jira.sakaiproject.org/browse/SAK-25776

* Start testing - There are three ways to test: Adopt-a-Tool, Jira 
filter, Detailed Test Plan [3].

Adopt-a-Tool [4]
If you have limited time to test, or if a particular tool is of high 
value to your institution, you might consider our Adopt-a-tool approach. 
Adopt a tool and test it on the QA server [6] as thoroughly as you can. 
If the tool works with other tools, I recommend you also test those 
integrations (esp. the gradebook integrations).

Jira filter  [5]
Once a bug has been fixed by our always-awesome world-wide volunteer 
developers, we like to test to make sure that fixes are working as 
intended and do not inadvertently cause other problems. Going through 
Jiras is also a quick way to test a single fix at a time, if your time 
is limited. The list is ordered by project, and then by priority.

Detailed Test Plan [3]
We especially love folks who sign up for detailed testing. Our detailed 
Test plan includes links to detailed test scripts, where available, and 
a list of the Jiras specific to the individual Tools. There is some 
overlap between the three ways of testing and that is okay. It all works 
out in the end.

[1] Code freeze means that no new features can be added to Sakai 10 from 
this point forward. String freeze means that updating translations for 
Sakai can commence. A release candidate is when the Sakai team thinks no 
more high priority bugs (aka blocker bugs) exist that would prevent the 
release. Often we need one or two final testing cycles after this point 
to feel confident we can release.

[2] Sakai-dev and sakai-qa lists, respectively - 
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev and 

[3] Sakai 10-qa03 test plan - 

[4] Adopt-a-Tool signup - http://bit.ly/sakai10adopt

[5] Jira filter - http://bit.ly/sakai10adopt

[6] List of QA servers - 

Please send any comments or questions to neal.caidin at apereo.org.


Neal Caidin
Sakai Community Coordinator
Apereo Foundation
neal.caidin at apereo.org
Skype me! (but let me know in advance for the first interaction) - nealkdin

More information about the production mailing list