Yu Zhen, Thanks for the report! We made big progress, thanks for every volunteers contribution!
One more think I suggest we to focus in the next week is the testing on Base and Drawing. The problem is that we don't have any existing test cases for Base and Drawing for now. So besides creating test cases from scratch, I think we can also try another way to do quick testing for these 2 applications: people do exploration test, and report in QA mail group on (1) covered platform/database; (2) tested scenario/steps; (3) test result/defect found. So that we can identify any ship blocker defects in Base and Drawing quickly. - Shenfeng (Simon) 2013/6/17 Yuzhen Fan <fanyuz...@gmail.com> > Hi All, > > We wrap up the AOO 4.0 Full Regression test this week, here is the weekly > update (6/10 - 6/14): > > *Test execution:* > 1. Testing of upgrading/updating a former AOO/OOo's version - Done and > Passed > 2. Acceptance testing on stlport change on Win7/Mac/RHEL/Ubuntu platforms > - Done and accepted, with none of the opening defects found from this > testing, is introduced by stlport. However, it needs development's > confirmation. > * > Defect summary:* > 1. 4.0.0 release blocker candidate defects are under reviewing, the total > number is 66 now (original is 90) > 2. Redhat specific defect with 64-bit Java, Bug 122485 ([Crash]OOO crash > when apply animation for table/chart object) gets resolved, will set QE to > verify > * > Issues & quality highlight:* > 1. Need to cover silent installation testing on Windows as it is not > included in previous testing > 2. The triage of bugs for AOO 4.0.0 release blockers is ongoing. > 3. QAs are reminded to retest the failed/blocked test executions as the > defects get fixed > > *Volunteer status: * > 1. No new volunteers(total 20 so far) on test execution work > 2. No new volunteers(total 6 so far) on defect work, the progress on > confirming defects are low, need more to clean backlog of unconfirmed and > resolved defects > > *Plan for next week:* > 1. Locate AOO MSI file for slient installation testing on Windows > 2. Work out test plan for AOO 4.0 Final Regression test and populate test > cases in Testlink as fixing defects > 3. Work with development to prioritize critical defects as 4.0.0 release > blockers and assign them to Dev volunteers > 4. Retest the failed/blocked test executions as the defects get fixed > > Thanks you all for effort on full regression testing, let's work together > to move to final regression testing! > > Regards, > Yu Zhen >
