[WG: Sakai QA] [Building Sakai] QA worksheets

[Berg, Alan]

Hi Dave,

If you have questions the distribution lists are very informative, the qa list sakai-qa and the dev list sakai-dev, the crowd is very knowledgeable and responsive.

Example test plans, selenium tests, provisioning web services and a little documentation, then try https://source.sakaiproject.org/contrib/qa/trunk/
Current QA information: http://confluence.sakaiproject.org/display/QA/Home
2.7 Testing cycle: http://confluence.sakaiproject.org/display/QA/QA+Testers+Wall, http://confluence.sakaiproject.org/display/QA/2.7.0+Changes
A number of indie projects have their own testing cycle, for example OSP: http://confluence.sakaiproject.org/display/OSP/OSP+Test+Scripts
I wish to motivate the sharing of test plans, idea's and scripts through either confluence or Subversion as this allows for ease of reuse by others.

Further, I would recommend creating an account on Jira the bug reporting database and searching http://jira.sakaiproject.org/secure/Dashboard.jspa

Finally, if you have any central QA related questions you are more than welcome to contract me. 


Alan

Alan Berg
Interim QA Director - The Sakai Foundation

Senior Developer / Quality Assurance
Group Education and Research Services
Central Computer Services
University of Amsterdam

http://home.uva.nl/a.m.berg




-----Original Message-----
From: sakai-dev-bounces at collab.sakaiproject.org on behalf of KHEY,DAVID NICOLAUS
Sent: Wed 2/17/2010 22:45
To: sakai-dev at collab.sakaiproject.org
Subject: [Building Sakai] QA worksheets
 
Hello developers,

First time writing to this list - and rather excited.  I have been charged with working towards building a QA/QC program for Sakai at the University of Florida.  Does anyone have any pre-existing worksheets/checklists of all the front-end tools that I can work off of to get our pilot instance up and running smoothly?

Please advise.  I did some searching on the QA wiki and only found a matrix with known bugs.  I am looking for a matrix of items to check by tool to assure that we can certify that the system is working as expected (post-restart, maintenance, etc).

We are running 2.6 and will plan hop on the 2.7 QA/QC team (and future testing teams) when we get our systems stabilized and deployed - I hope to get better acquainted with the QA team before then.

Thanks everyone!
Dave

--
David N. Khey, Ph.D., M.S.
Staff
eLearning Support Services, Academic Technology
University of Florida


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20100218/16ce3db0/attachment.html