This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • AOO 4.1 Testing Plan
Skip to end of metadata
Go to start of metadata

The following table is intended to list different test phases and the corresponding frequency, method and coverage with them

Testing Process

Test Phase

Frequency

Method

Coverage

BVT (Build Verification Test)

Weekly

Automated

Basic operations in Writer, Calc and Impress

FVT (Function Verification Test)

AOO 4.1 development phase

Manual

1. Basic, advanced, complicated operations in Writer, Calc and Impress, including features in 4.1 Proposed Release Contents in AOO 4.1 Release Planning

2. Impact area testing by changes/fixes made

Full Pass RegressionAOO 4.1 after Beta releaseManual

1. Basic, advanced operations in Writer, Calc and Impress, including features in 4.1 Proposed Release Contents in AOO 4.1 Release Planning

2. Impact area testing by changes/fixes made

Final RegressionMerged with FPRManualDitto
RC Acceptance TestAOO 4.1 after RC releaseManual1. Basic operations in Writer, Calc and Impress

PVT

Monthly

Automated

1. Basic operation like new/load/save/close in Writer, Calc and Impress, to collect the consumed time/memory/handle

2. GUI source code from our subversion repository: https://svn.apache.org/repos/asf/openoffice/trunk/test/

AVT

AOO 4.1 development phase

Automate/Manual

Compliance with ACC checklist (IBM software accessibility checklist)

 

The following table list the test platforms and the coverage rate in different test phases

Testing Platforms

Platform

Coverage (FVT)Coverage (FPR, FR and RCAT)Coverage (PVT)

Windows 7

25%

15%

100%

Windows 8

25%

15%

 

Redhat Linux 32bit

10%

5%

 

Redhat Linux 64bit

30%

20%

 

Ubuntu Linux 64bit

30%

20%

100%

Mac OS X 10.8/10.9

30%

25%

 

Total

150%

100%

100% +

 

The following table is intended to collect and document testing to new features, enhancements or other working areas related to the AOO 4.1 release testing

The status can be tracked highlevel for example by using the colors ok/done, in progress and open/missing .

More detailed testing material(test scenarios / steps) can be found in Testlink, defects found during testing can be found in Bugzilla

Testing Contents

Priority

Item

Feature/Enhancement

Testing way

Volunteer(s)

Status

Comment

1Accessibility support (iAccessibiltiy2 support to improve the usability)New Feature

Test with ACC checklist based on BVT scenarios

Create and execute test cases in Teslink,

Liu Ping TanDone 
 

Patch Mechanism in Windows

New Feature

 

 

 

 

 

AOO Security Features without Mozilla

 

 

 

 

 
 

Icon update

Enhancement

https://cwiki.apache.org/confluence/display/OOOUSERS/AOO4.1+-+Desktop+Icons

 

 

 

1

In-place editing of Input Fields

Enhancement

I am working on a solution for issue 33737 [1] and I am making good progress.
I have started the documentation of the solution in our wiki - please have a look at https://wiki.openoffice.org/wiki/Writer/Input_Fields. It should be almost complete - may be I have forgotten the one or the other which will follow when I get notice of its missing.
If you are interested in this area, please have a look and provide feedback.
Thanks in advance.

Liu Ping Tan

  
 

Integrating OOXML enhancement from the OSBA patch

New Feature

 

 

 

 

1

use case 4 - comments/annotations on text ranges

Yu Zhen FanIn Progress 
 

genLang / New translation workflow

 

No test from QA

 

 

 

 

build.pl / central Makefile instead of build.pl

 

No test from QA

 

 

 

 

Mac / 64bit OSX Support

 

 

Volunteers

 

 
 

new MacOS Mavericks OS Support

 

Repeat basic functional test

 

Done

 

1Existing functions in 3 Apps (FVT)Legacy FeatureExecute test cases in Teslink, In Progress 
 

Create test documents in OOXML format

Enhancement

Create test cases in Testlink

Upload test documents to svn

Yu Zhen Fan

Liu Ping Tan

Jing Long Wu

In Progress 
 

Presentation template validation

Legacy Feature

1. Import a template to AOO to see if it displays well without any mess

2. Create a new presentation with this template in AOO to see if it works

3. Apply this template to an existing presentation in AOO to see if it work

(pay particular attention to the Styles and check how they are applied in the templates, particularly with paragraph, bullets, numbering etc.)

Yu Zhen FanIn Progress 
 

Develop manual test cases for Base

EnhancementCreate test cases in TestlinkYu Zhen Fan and VolunteersIn Progress 
 

Get more people who have interest to be familiar with the test automation

N/ADocument test guidanceLiu Ping Tan and VolunteersIn Progress 
  • No labels