You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Yuzhen Fan <fa...@gmail.com> on 2013/06/17 14:50:38 UTC
[QA][Test Report] Weekly Status Update as of 20130614
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
Re: [QA][Test Report] Weekly Status Update as of 20130614
Posted by Yuzhen Fan <fa...@gmail.com>.
Simon and All,
This is call for volunteers to do exploration test on Base / Drawing and
write test cases for Base / Drawing:
1. About writing test cases for Base, I have completed to create
hierarchies of test suites in TestLink based on the finalized test matrix
http://wiki.openoffice.org/wiki/QA/Tescase. Please could volunteers
navigate the test suite tree view in the Test Specification (Test Project
is Apache OpenOffice testproject), and let's following below process to
organize test case writing:
1) Volunteers provide their TestLink ID and list of their preferred test
suites to Yu Zhen (Currently I have Anil Kumar's TestLink ID and
confirmation to write test cases)
2) Yu Zhen specifies the test suites' assignment to the individual volunteer
3) Volunteers write test cases in the assigned test suites, in TestLink.
For test cases related to connectivity testing, please attach the "live"
test DB(s) and provide steps to set up test environment in "Preconditions".
It's encouraged test cases' author to test his/her test cases in execution
stage.
2. I will work with Liu Ping on test matrix for Drawing later this week, if
you have interest on Drawing test case writing, please let me know, I will
book for you
3. I will consolidate exploration test reports on Base and Drawing from
volunteers, and then incorporate to test case writing. Please see details
on how to do as below (proposed by Simon):
people do exploration test, and report in QA mail group on (1) covered
platform/database; (2) tested scenario/steps; (3) test result/defect found
Regards,
Yu Zhen
On Tue, Jun 18, 2013 at 11:35 AM, Shenfeng Liu <li...@gmail.com> wrote:
> 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 <fa...@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
> >
>
Re: [QA][Test Report] Weekly Status Update as of 20130614
Posted by Yuzhen Fan <fa...@gmail.com>.
Simon and All,
This is call for volunteers to do exploration test on Base / Drawing and
write test cases for Base / Drawing:
1. About writing test cases for Base, I have completed to create
hierarchies of test suites in TestLink based on the finalized test matrix
http://wiki.openoffice.org/wiki/QA/Tescase. Please could volunteers
navigate the test suite tree view in the Test Specification (Test Project
is Apache OpenOffice testproject), and let's following below process to
organize test case writing:
1) Volunteers provide their TestLink ID and list of their preferred test
suites to Yu Zhen (Currently I have Anil Kumar's TestLink ID and
confirmation to write test cases)
2) Yu Zhen specifies the test suites' assignment to the individual volunteer
3) Volunteers write test cases in the assigned test suites, in TestLink.
For test cases related to connectivity testing, please attach the "live"
test DB(s) and provide steps to set up test environment in "Preconditions".
It's encouraged test cases' author to test his/her test cases in execution
stage.
2. I will work with Liu Ping on test matrix for Drawing later this week, if
you have interest on Drawing test case writing, please let me know, I will
book for you
3. I will consolidate exploration test reports on Base and Drawing from
volunteers, and then incorporate to test case writing. Please see details
on how to do as below (proposed by Simon):
people do exploration test, and report in QA mail group on (1) covered
platform/database; (2) tested scenario/steps; (3) test result/defect found
Regards,
Yu Zhen
On Tue, Jun 18, 2013 at 11:35 AM, Shenfeng Liu <li...@gmail.com> wrote:
> 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 <fa...@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
> >
>
Re: [QA][Test Report] Weekly Status Update as of 20130614
Posted by Shenfeng Liu <li...@gmail.com>.
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 <fa...@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
>