Overview

This QA plan if for AOO 3.4 release, currently it covers both QA related works and the detail AOO 3.4 testing plan.

QA related works:

  1. Focus on establishing automation mechanism. Start from Build Verification Testing (BVT in short).
  2. Focus on test infrastructure set up. Start from case management tool. For 3.4.0, place the test cases on wiki and volunteer can do general testing against. If volunteer could not write cases, may give the test scope he would do. For example, which component etc. And then report defects in Apache Bugzilla .
  3. Focus on Performance Verification Testing (PVT in short) investigation, and setup benchmark PVT environment.
  4. Establish QA entry in AOO wiki (Use https://cwiki.apache.org/ for QA and test plan. http://wiki.services.openoffice.org/ for QA entry and related test cases and test results)
  5. Build private build before official build is ready
  6. The following platforms will be covered (please keep the general system requirements in mind):

AOO 3.4 test plan:
The code changes occur in AOO 3.4:

  1. IP clearance
  2. AOO 3.4 content code change
  3. Bug fix

Based on above code changes, four kinds of testing should be done before publish AOO 3.4.0 GA to community:

  1. Leverage solid QA contributors on IP clearance impact functional verification testing
  2. Leverage OpenOffice users on AOO 3.4 content code change testing
  3. Leverage OpenOffice users on General Usage regression test
  4. Leverage solid QA contributors and OpenOffice users on critical bug fixes verification and impact area testing.
    The bug fix related impact area testing may combine with general usage regression testing.
Main platforms

64 bit version is preferred over 32 bit version.

Additional platforms