Presentation on theme: "What does Quality Assurance Mean to Sakai?"— Presentation transcript:
1 What does Quality Assurance Mean to Sakai? Megan MaySakai Quality Assurance Director
2 Role of QA Director Coordination! Help bring parties interested in the same testing efforts togetherFoster initiatives that support quality throughout the communityAssist in bridging the gap between test and design & development teamsEnsure release activities are transparent
3 WG Membership 2.2.1 23 People 10 Institutions 4 Countries 2.2.0 2.3.044 People17 Institutions5 Countries2.4.093 People37 Institutions11 Countries253 members on collab.Close to 100 participants for However, there is typically a core group in the WG testing (~20)
4 QA Participants for 2.4Vincent Siveton, Steve Swinsburg
5 QA Network Amsterdam Boston Cambridge Cape Town Columbia Indiana rSmartThere are 8 QA servers hosted at 7 institutions.Coming soon . . An oracle backend configured for spanish.
6 Where does QA fit in? What kinds of activities occur? Focus on Functional TestingPartners with accessibility WGAt end of the cycle. Usually other two cycle are beginning to occur while we’re still testing and preparing for the release.How we’ve been releasing back to backA lot of the release/product management is blurring into the QA process
13 Strides Forward Deployment testing on wider variety of platforms Data retention & conversion script testingIntegration of Accessibility WG activities in general QA cyclePush out testing earlierAutomated testing toolsStatic code reviewSelenium usageSite Profiles
14 Reflection on Release process Speak about the idea to have a phased release process.Maintenance Branches - deliver Foundation endorsed maintenance releases every 4-6 week
15 Proposed Kernel + Bundle Release Timing DevKernelQABundle DevelopmentPatchWeekBundle QAContrib X DevelopmentQAContrib Y DevelopmentQAContrib Z DevelopmentQAgoing to be more conservative about releases and freezes. Can use post-branches to get functionality out post freeze/release. Key is that we want community QA to run smoothly so our released products are nice and solid - while at the same time skilled sites can have the good stuff year-round :)NovReleaseUIFreezeAPIFreezeCodeFreezeMayRelease
16 Perceived Quality Level Various stakeholders in the community were polled. Data came from a pool of roughly 200 individuals. Mostly it’s equally
17 Quality, like beauty, is clearly in the eyes of the beholder.
19 What we can do! Infiltration of entire development process Formulate Working GroupsRefine processes & grow WGAreas where QA is neededMove more of the testing outside of the official QA cycle
20 Pledge Resources Why? Easy point of entry into Sakai What happens in the community has a direct local impactEasy point of entry into SakaiOne of the easier ways for people to contribute into Sakai-- Takes time to learn the software - a good tester is an informed testerOnly 86% issue verification - and this is of BUGSWhat happens in the community has a direct local impact
22 Other Sessions of Interest Expanding Community: Student Involvement in QA Testing (today, immediately following)Toward Further Automation of the Quality Assurance cycle (Thursday, 9:35-10:05 in Matterhorn 2)Sakai Accessibility Update (Thursday, 2:05-2:35 in Zurich 1)