Apache OpenOffice Wiki - User contributions [en]

QA/BVT Report

2013-11-12T08:29:31Z

Liupingtan: /* Result */

==Instruction==
* Platform: Platform which you can run BVT. 
* Volunteer: Volunteer's name to take this execution task. 
* Revision: build version of AOO4.0 
* Status: Passed/Failed 
* Bug ID:Issue number on Bugzilla which confirmed after manual test. 

For example:
{| class="wikitable" border="1"
|-
! Revision
! Platform
! Volunteer
! Status
! Bug ID
|-
| Rev. 1463876
| Windows7 64bit
| Li Feng Wang
| Passed
|
|-
| Rev. 1463876
| Windows7 32bit
| Li Feng Wang
| Passed
|
|}

{| class="wikitable" border="1"
|-
! Revision
! Platform
! Volunteer
! Status
! Bug ID
|-
| Rev. 1467162
| Windows7 64bit
| Li Feng Wang
| Failed
|[https://issues.apache.org/ooo/show_bug.cgi?id=120171 Bug 120171]
|-
| Rev. 1467162
| Windows7 32bit
| Li Feng Wang
| Passed
|
|}

==Result==
{| class="wikitable" border="1"
|-
! Revision
! Platform
! Volunteer
! Status
! Bug ID
|-
|
| WindowsXP
|
|
|
|-
|
| Windows7 32bit
|
|
|
|-
|2013-04-26_18:12 - Rev. 1476029
|Windows7 64bit
|liuping
|pass
|
|-
|2013-04-23_04:10:35 - Rev. 1454390
|Ubuntu 32 bits
|YACT
|passed
|
|-
|2013-05-8_11:20:23 - Rev. 1479578
|Ubuntu 64 bits
|YACT
|passed
|
|-
|
|Suse
|
|
|

|-
|
|Redhat
|
|
|

|-
|
|Mac
|
|
|

|-
|
|Debian 32bits
|
|
|

|-
|2013-04-12_04:12:12 - Rev. 1467162
|Debian 64bits
|filhocf
|[http://people.apache.org/~filhocf/aoo/bvt/result.html passed]
|

|-
|2013-11-12_04:06 -Rev. 1540658
|Windows7 64bit
|liuping
|passed
|
|}

[[Category:Quality Assurance]]

QA/BVT Report

2013-11-12T08:29:07Z

Liupingtan: /* Result */

==Instruction==
* Platform: Platform which you can run BVT. 
* Volunteer: Volunteer's name to take this execution task. 
* Revision: build version of AOO4.0 
* Status: Passed/Failed 
* Bug ID:Issue number on Bugzilla which confirmed after manual test. 

For example:
{| class="wikitable" border="1"
|-
! Revision
! Platform
! Volunteer
! Status
! Bug ID
|-
| Rev. 1463876
| Windows7 64bit
| Li Feng Wang
| Passed
|
|-
| Rev. 1463876
| Windows7 32bit
| Li Feng Wang
| Passed
|
|}

{| class="wikitable" border="1"
|-
! Revision
! Platform
! Volunteer
! Status
! Bug ID
|-
| Rev. 1467162
| Windows7 64bit
| Li Feng Wang
| Failed
|[https://issues.apache.org/ooo/show_bug.cgi?id=120171 Bug 120171]
|-
| Rev. 1467162
| Windows7 32bit
| Li Feng Wang
| Passed
|
|}

==Result==
{| class="wikitable" border="1"
|-
! Revision
! Platform
! Volunteer
! Status
! Bug ID
|-
|
| WindowsXP
|
|
|
|-
|
| Windows7 32bit
|
|
|
|-
|2013-04-26_18:12 - Rev. 1476029
|Windows7 64bit
|liuping
|pass
|
|-
|2013-04-23_04:10:35 - Rev. 1454390
|Ubuntu 32 bits
|YACT
|passed
|
|-
|2013-05-8_11:20:23 - Rev. 1479578
|Ubuntu 64 bits
|YACT
|passed
|
|-
|
|Suse
|
|
|

|-
|
|Redhat
|
|
|

|-
|
|Mac
|
|
|

|-
|
|Debian 32bits
|
|
|

|-
|2013-04-12_04:12:12 - Rev. 1467162
|Debian 64bits
|filhocf
|[http://people.apache.org/~filhocf/aoo/bvt/result.html passed]
|

|-
|2013-11-12_04:06 -Rev. 1540658
|Windows7 64bits
|liuping
|passed
|
|}

[[Category:Quality Assurance]]

QA/BVT Report

2013-11-12T01:06:27Z

Liupingtan: /* Instruction */

QA/BVT Report

2013-11-12T01:06:09Z

Liupingtan: /* Instruction */

==Instruction==
* Platform: Platform which you can run BVT. 
* Volunteer: Volunteer's name to take this execution task. 
* Revision: build version of AOO4.0 
* Status: Passed/Failed 
* Bug ID:Issue number on Bugzilla which confirmed after manual test. 

For example:
{| class="wikitable" border="1"
|-
! Revision
! Platform
! Volunteer
! Status
! Bug ID
|-
| Rev. 1463876
| Windows7 64bit
| Li Feng Wan
| Passed
|
|-
| Rev. 1463876
| Windows7 32bit
| Li Feng Wang
| Passed
|
|}

{| class="wikitable" border="1"
|-
! Revision
! Platform
! Volunteer
! Status
! Bug ID
|-
| Rev. 1467162
| Windows7 64bit
| Li Feng Wang
| Failed
|[https://issues.apache.org/ooo/show_bug.cgi?id=120171 Bug 120171]
|-
| Rev. 1467162
| Windows7 32bit
| Li Feng Wang
| Passed
|
|}

==Result==
{| class="wikitable" border="1"
|-
! Revision
! Platform
! Volunteer
! Status
! Bug ID
|-
|
| WindowsXP
|
|
|
|-
|
| Windows7 32bit
|
|
|
|-
|2013-04-26_18:12 - Rev. 1476029
|Windows7 64bit
|liuping
|pass
|
|-
|2013-04-23_04:10:35 - Rev. 1454390
|Ubuntu 32 bits
|YACT
|passed
|
|-
|2013-05-8_11:20:23 - Rev. 1479578
|Ubuntu 64 bits
|YACT
|passed
|
|-
|
|Suse
|
|
|

|-
|
|Redhat
|
|
|

|-
|
|Mac
|
|
|

|-
|
|Debian 32bits
|
|
|

|-
|2013-04-12_04:12:12 - Rev. 1467162
|Debian 64bits
|filhocf
|[http://people.apache.org/~filhocf/aoo/bvt/result.html passed]
|
|}

[[Category:Quality Assurance]]

File:Example1.jpeg

2013-09-18T07:12:08Z

Liupingtan: Liupingtan uploaded a new version of "File:Example1.jpeg"

QA/AOO401 PVT GUI Result/r1521921 Windows7

2013-09-18T07:03:07Z

Liupingtan:

'''GUI PVT''' is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation

'''Test Environment:''' Windows7; CPU:2.6 GHz; Mem: 8GB

'''Test Build:''' AOO.4.0.1_r1521921 '''Test Baseline Build:''' AOO4.0_r1503704

'''Test Evaluation Method:''' Automatically run each test case 8 times
and compute the average value of 5 times (excluding the first round result, the minimum and maximum result).

About Consumed Time

'''1''' Most of result indicated that the performance had been improved especially for XLS

'''2''' One pretty bad result about loadFinishComplexDOCX is more than 20%

'''3''' The reference information and material data

http://wiki.openoffice.org/wiki/File:Example1.jpeg

[[Category:Quality Assurance]]

QA/AOO401 PVT GUI Result/r1521921 Windows7

2013-09-18T07:00:04Z

Liupingtan:

'''GUI PVT''' is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation

'''Test Environment:''' Windows7; CPU:2.6 GHz; Mem: 8GB

'''Test Build:''' AOO.4.0.1_r1521921 '''Test Baseline Build:''' AOO4.0_r1503704

'''Test Evaluation Method:''' Automatically run each test case 8 times
and compute the average value of 5 times (excluding the first round result, the minimum and maximum result).

About Consumed Time

'''1''' Most of result indicated that the performance had been improved especially for XLS

'''2''' One pretty bad result about loadFinishComplexDOCX is more than 20%

'''3''' The reference information and material data

[[File:Rev1521921.png|thumb]]

[[Category:Quality Assurance]]

QA/AOO401 PVT GUI Result/r1521921 Windows7

2013-09-18T06:58:45Z

Liupingtan:

'''GUI PVT''' is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation

'''Test Environment:''' Windows7; CPU:2.6 GHz; Mem: 8GB

'''Test Build:''' AOO.4.0.1_r1521921 '''Test Baseline Build:''' AOO4.0_r1503704

'''Test Evaluation Method:''' Automatically run each test case 8 times
and compute the average value of 5 times (excluding the first round result, the minimum and maximum result).

About Consumed Time

'''1''' Most of result indicated that the performance had been improved especially for XLS

'''2''' One pretty bad result about loadFinishComplexDOCX is more than 20%

'''3''' The reference information and material data

[[File:Example1.png|thumb|Caption text]]

[[Category:Quality Assurance]]

QA/AOO401 PVT GUI Result/r1521921 Windows7

2013-09-18T06:57:32Z

Liupingtan:

'''GUI PVT''' is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation

'''Test Environment:''' Windows7; CPU:2.6 GHz; Mem: 8GB

'''Test Build:''' AOO.4.0.1_r1521921 '''Test Baseline Build:''' AOO4.0_r1503704

'''Test Evaluation Method:''' Automatically run each test case 8 times
and compute the average value of 5 times (excluding the first round result, the minimum and maximum result).

About Consumed Time

'''1''' Most of result indicated that the performance had been improved especially for XLS

'''2''' One pretty bad result about loadFinishComplexDOCX is more than 20%

'''3''' The reference information and material data

<gallery>
File:Example1.png|Caption 2
</gallery>
[[Category:Quality Assurance]]

QA/AOO401 PVT GUI Result/r1521921 Windows7

2013-09-18T06:56:38Z

Liupingtan:

'''GUI PVT''' is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation

'''Test Environment:''' Windows7; CPU:2.6 GHz; Mem: 8GB

'''Test Build:''' AOO.4.0.1_r1521921 '''Test Baseline Build:''' AOO4.0_r1503704

'''Test Evaluation Method:''' Automatically run each test case 8 times
and compute the average value of 5 times (excluding the first round result, the minimum and maximum result).

About Consumed Time

'''1''' Most of result indicated that the performance had been improved especially for XLS

'''2''' One pretty bad result about loadFinishComplexDOCX is more than 20%

'''3''' The reference information and material data

[[File:Example1.png|thumb|Caption 2]]
[[Category:Quality Assurance]]

File:Example1.jpeg

2013-09-18T06:55:37Z

Liupingtan: Liupingtan uploaded a new version of "File:Example1.jpeg"

File:Example1.jpeg

2013-09-18T06:55:32Z

Liupingtan: Liupingtan uploaded a new version of "File:Example1.jpeg"

File:Example1.jpeg

2013-09-18T06:55:21Z

Liupingtan:

QA/AOO401 PVT GUI Result/r1521921 Windows7

2013-09-18T06:41:59Z

Liupingtan:

'''GUI PVT''' is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation

'''Test Environment:''' Windows7; CPU:2.6 GHz; Mem: 8GB

'''Test Build:''' AOO.4.0.1_r1521921 '''Test Baseline Build:''' AOO4.0_r1503704

'''Test Evaluation Method:''' Automatically run each test case 8 times
and compute the average value of 5 times (excluding the first round result, the minimum and maximum result).

About Consumed Time

'''1''' Most of result indicated that the performance had been improved especially for XLS

'''2''' One pretty bad result about loadFinishComplexDOCX is more than 20%

'''3''' The reference information and material data

[[File:Example1.png|thumb|Caption text]]
[[Category:Quality Assurance]]

QA/AOO401 PVT GUI Result/r1521921 Windows7

2013-09-18T06:36:32Z

Liupingtan:

'''GUI PVT''' is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation

'''Test Environment:''' Windows7; CPU:2.6 GHz; Mem: 8GB

'''Test Build:''' AOO.4.0.1_r1521921 '''Test Baseline Build:''' AOO4.0_r1503704

'''Test Evaluation Method:''' Automatically run each test case 8 times
and compute the average value of 5 times (excluding the first round result, the minimum and maximum result).

About Consumed Time

'''1''' Most of result indicated that the performance had been improved especially for XLS

'''2''' One pretty bad result about loadFinishComplexDOCX is more than 20%

'''3''' The reference information and material data

<gallery>
File:GUI r1521921.jpg|Caption2
</gallery>

[[Category:Quality Assurance]]

QA/AOO401 PVT GUI Result/r1521921 Windows7

2013-09-18T06:33:54Z

Liupingtan: Created page with " GUI PVT is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation Test Environment: Win..."

GUI PVT is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation

Test Environment: Windows7; CPU:2.6 GHz; Mem: 8GB
Test Build: AOO.4.0.1_r1518667 Test Baseline Build: AOO4.0_r1503704
Test Evaluation Method: Automatically run each test case 8 times and compute the average value of 5 times (excluding the first round result, the minimum and maximum result).

About Consumed Time
1 Most of result indicated that the performance had been improved especially for XLS
2 One pretty bad result about loadFinishComplexDOCX is more than 20%
3 The reference information and material data

QA/AOO401 PVT GUI Result/r1518667 Windows7

2013-09-16T05:53:55Z

Liupingtan:

'''GUI PVT''' is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation

'''Test Environment:''' Windows7; CPU:2.6 GHz; Mem: 8GB

'''Test Build:''' AOO.4.0.1_r1518667 '''Test Baseline Build:''' AOO4.0_r1503704

'''Test Evaluation Method:''' Automatically run each test case 8 times
and compute the average value of 5 times (excluding the first round result, the minimum and maximum result).

About Consumed Time

'''1''' Most of result indicated that the performance had been improved especially for XLS

'''2''' Some bad result but less than 5% ,which should be acceptable

'''3''' The reference information and material data

<gallery>
File:GUI 2.jpg|Caption2
</gallery>

[[Category:Quality Assurance]]

File:GUI 2.jpg

2013-09-16T05:52:47Z

Liupingtan: Liupingtan uploaded a new version of "File:GUI 2.jpg"

[[Category:Screenshots and Dialogs]]

QA/PVT Report

2013-09-16T05:46:04Z

Liupingtan: /* PVT_GUI report on 4.0.1_Dev_r1518667 */

==PVT_GUI report on 4.0.1_Dev_r1518667==
[[QA/AOO401_PVT_GUI_Result/r1518667_Windows7]]

==PVT_GUI report on 4.0.1_Dev_r1521921==
[[QA/AOO401_PVT_GUI_Result/r1521921_Windows7]]
[[Category:Quality Assurance]]

QA/AOO401 PVT GUI Result/r1518667 Windows7

2013-09-06T08:39:03Z

Liupingtan:

'''GUI PVT''' is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation

'''Test Environment:''' Windows7; CPU:2.6 GHz; Mem: 8GB

'''Test Build:''' AOO.4.0.1_r1518667 '''Test Baseline Build:''' AOO4.0_r1503704

'''Test Evaluation Method:''' Automatically run each test case 8 times
and compute the average value of 5 times (excluding the first round result, the minimum and maximum result).

About Consumed Time

'''1''' Most of result indicated that the performance had been improved especially for XLS

'''2''' Some bad result but less than 5% ,which should be acceptable

'''3''' The reference information and material data

<gallery>
File:Example.jpg|Caption1
File:GUI 2.jpg|Caption2
</gallery>

QA/AOO401 PVT GUI Result/r1518667 Windows7

2013-09-06T08:38:05Z

Liupingtan:

'''GUI PVT''' is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation

'''Test Environment:''' Windows7; CPU:2.6 GHz; Mem: 8GB

'''Test Build:''' AOO.4.0.1_r1518667 '''Test Baseline Build:''' AOO4.0_r1503704

'''Test Evaluation Method:''' Automatically run each test case 8 times
and compute the average value of 5 times (excluding the first round result, the minimum and maximum result).

About Consumed Time

'''1''' Most of result indicated that the performance had been improved especially for XLS
'''2''' Some bad result but less than 5% ,which should be acceptable
'''3''' The reference information and material data

<gallery>
File:Example.jpg|Caption1
File:GUI 2.jpg|Caption2
</gallery>

QA/AOO401 PVT GUI Result/r1518667 Windows7

2013-09-06T08:28:12Z

Liupingtan:

'''GUI PVT''' is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation

'''Test Environment:''' Windows7; CPU:2.6 GHz; Mem: 8GB

'''Test Build:''' AOO.4.0.1_r1518667 '''Test Baseline Build:''' AOO4.0_r1503704

'''Test Evaluation Method:''' Automatically run each test case 8 times
and compute the average value of 5 times (excluding the first round result, the minimum and maximum result).

About Consumed Time

<gallery>
File:Example.jpg|Caption1
File:GUI 2.jpg|Caption2
</gallery>

QA/AOO401 PVT GUI Result/r1518667 Windows7

2013-09-06T08:25:31Z

Liupingtan:

QA/AOO401 PVT GUI Result/r1518667 Windows7

2013-09-06T08:23:41Z

Liupingtan:

'''GUI PVT''' is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation

'''Test Environment:''' Windows7; CPU:2.6 GHz; Mem: 8GB

'''Test Build:''' AOO.4.0.1_r1518667 '''Test Baseline Build:''' AOO4.0_r1503704

'''Test Evaluation Method:''' Automatically run each test case 8 times
and compute the average value of 5 times (excluding the first round result, the minimum and maximum result).

<gallery>
File:Example.jpg|Caption0
File:GUI 1.jpg|Caption1
File:GUI 2.jpg|Caption2
</gallery>

QA/AOO401 PVT GUI Result/r1518667 Windows7

2013-09-06T08:22:52Z

Liupingtan:

QA/AOO401 PVT GUI Result/r1518667 Windows7

2013-09-06T08:18:36Z

Liupingtan:

File:GUI 2.jpg

2013-09-06T08:17:40Z

Liupingtan:

QA/AOO401 PVT GUI Result/r1518667 Windows7

2013-09-06T08:15:37Z

Liupingtan:

QA/AOO401 PVT GUI Result/r1518667 Windows7

2013-09-06T08:13:17Z

Liupingtan:

File:Example.r1518667 Windows7.jpg

2013-09-06T08:12:24Z

Liupingtan: Liupingtan uploaded a new version of "File:Example.jpg"

current color picker dialog

[[Category:Screenshots and Dialogs]]

QA/AOO401 PVT GUI Result/r1518667 Windows7

2013-09-06T08:09:30Z

Liupingtan:

QA/AOO401 PVT GUI Result/r1518667 Windows7

2013-09-06T08:08:26Z

Liupingtan:

QA/AOO401 PVT GUI Result/r1518667 Windows7

2013-09-06T08:03:56Z

Liupingtan:

-GUI PVT is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation[New/loading/saving documents]
--Test Environment: Windows7 ,CPU:2.6 GHz; Mem: 8GB
--Test Build: AOO.4.0.1_r1518667; Baseline AOO4.0_r1503704
--Test Evaluation Method:Automatically run each test case 8 times and compute the average value of 5 times (excluding the first round result, the minimum and maximum result).

QA/AOO401 PVT GUI Result/r1518667 Windows7

2013-09-06T08:03:26Z

Liupingtan:

GUI PVT is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation[New/loading/saving documents]
Test Environment: Windows7 ,CPU:2.6 GHz; Mem: 8GB
Test Build: AOO.4.0.1_r1518667; Baseline AOO4.0_r1503704
Test Evaluation Method:Automatically run each test case 8 times and compute the average value of 5 times (excluding the first round result, the minimum and maximum result).

QA/AOO401 PVT GUI Result/r1518667 Windows7

2013-09-06T08:01:34Z

Liupingtan: Created page with " <gallery> File:Example.jpg|Caption1 File:Example.jpg|Caption2 </gallery>"

<gallery>
File:Example.jpg|Caption1
File:Example.jpg|Caption2
</gallery>

QA/PVT

2013-09-06T07:42:21Z

Liupingtan: /* Run testing */

= Introduction =
Performance Verification Test, PVT for short, is a set of tests that run on new build to get the performance indicators of AOO. Performance indicators include consumed time/memory/handle after some operations. 
PVT of AOO consists of two parts: GUI and UNO. 
=== GUI PVT ===
GUI PVT is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation. 
=== UNO PVT ===
UNO PVT is to use UNO API to do basic documents operations, such as loading/saving/closing documents, then count the consumed time. 

You can view daily PVT report here: [http://people.apache.org/~liuzhe/testdashboard/#pvt] 

= Prerequisites =
==Platform==
Test machine with OS in below list:
WindowsXP, Windows7 32bit, Windows7 64bit,Ubuntu, Suse, Redhat,Mac

==AOO Build==
AOO4.0 [http://ci.apache.org/projects/openoffice/index.html build snapshots] 
AOO4.0.1 Development Build [https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds]

==Environment tools==
*SVN Client:
On Windows: Download and Install TortoiseSVN as SVN Client to checkout sourcecode. 
[http://tortoisesvn.net/downloads.html http://tortoisesvn.net/downloads.html] 
*JDK: [http://java.sun.com/javase/6/ JDK 1.6] or above. 
*Ant: [http://ant.apache.org/bindownload.cgi Apache Ant 1.8.2] or above.

==Soft Skills==
*Basic skills about Windows Command line, Linux/Mac Terminal
*Basic knowledge of Java

=How to run PVT automatically=
== Getting the source code ==
Anyone can checkout source code from our Subversion repository. Run the following command.
svn co https://svn.apache.org/repos/asf/openoffice/trunk/test/ test

On Windows, you can use TortoiseSVN GUI Client to checkout, URL of repository is https://svn.apache.org/repos/asf/openoffice/trunk/test/
== Run testing ==
'''As a normal user, how to run testing against an installed OpenOffice?''' 
Firstly compile the project with the command under test module.
ant -Dopenoffice.home="OpenOffice installation directory" compile
Then start testing with the command "run".
e.g. Run the given test classes
run -Dopenoffice.home="/Applications/OpenOffice.org.app/Contents" -tc pvt.gui.Benchmark

''' Where to get the testing result? '''

By default, the testing output is stored in "test/testspace/output***". Open "test/testspace/output/" in your browser to see the testing report. 

Special stuff in the output directory.
pvt.gui.Benchmark:Test result in XML. Every case Every repeat's detail result
screenshot/: Screenshot pictures when test assert is failed.

==Sample on Windows==
Running Platform: Windows 7 64bit
*Install OO, use default install directory. "C:/Program Files (x86)/OpenOffice.org 4 "
*Checkout sourcecode to "C:\test"
*Change CMD directory to "C:\test",then compile test use: ant -Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4" compile
*Change CMD directory to "C:\test",then execute PVT: run -Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4 " -tc pvt.uno.Conversion

==FAQ==

{{Template:Documentation/Note| '''What is openoffice.home?''' 
The default installation directory of Apache OpenOffice: 
Mac OS X: "/Applications/OpenOffice.org.app/Contents" 
Linux: "/opt/openoffice.org4" 
Windows: "C:/Program Files/OpenOffice.org 4" 
Windows 64b: "C:\Program Files (x86)\OpenOffice 4"
}}
{{Template:Documentation/Note| '''Can I do other operations when PVT Gui is running?''' 
For PVT Gui cases wrote via GUI(Graphical User Interface) not UNO interface, little display offset may impact test result. So not do other operations when PVT is running.
}}
{{Template:Documentation/Note| '''Do I need compile pvt source code anytime?''' 
If there is not any change of pvt source code, there is no need to compile it anytime.
That is "Java is compile once, run everywhere"
}}

[[Category:Quality Assurance]]

QA/PVT

2013-09-06T07:41:24Z

Liupingtan: /* Run testing */

= Introduction =
Performance Verification Test, PVT for short, is a set of tests that run on new build to get the performance indicators of AOO. Performance indicators include consumed time/memory/handle after some operations. 
PVT of AOO consists of two parts: GUI and UNO. 
=== GUI PVT ===
GUI PVT is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation. 
=== UNO PVT ===
UNO PVT is to use UNO API to do basic documents operations, such as loading/saving/closing documents, then count the consumed time. 

You can view daily PVT report here: [http://people.apache.org/~liuzhe/testdashboard/#pvt] 

= Prerequisites =
==Platform==
Test machine with OS in below list:
WindowsXP, Windows7 32bit, Windows7 64bit,Ubuntu, Suse, Redhat,Mac

==AOO Build==
AOO4.0 [http://ci.apache.org/projects/openoffice/index.html build snapshots] 
AOO4.0.1 Development Build [https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds]

==Environment tools==
*SVN Client:
On Windows: Download and Install TortoiseSVN as SVN Client to checkout sourcecode. 
[http://tortoisesvn.net/downloads.html http://tortoisesvn.net/downloads.html] 
*JDK: [http://java.sun.com/javase/6/ JDK 1.6] or above. 
*Ant: [http://ant.apache.org/bindownload.cgi Apache Ant 1.8.2] or above.

==Soft Skills==
*Basic skills about Windows Command line, Linux/Mac Terminal
*Basic knowledge of Java

=How to run PVT automatically=
== Getting the source code ==
Anyone can checkout source code from our Subversion repository. Run the following command.
svn co https://svn.apache.org/repos/asf/openoffice/trunk/test/ test

On Windows, you can use TortoiseSVN GUI Client to checkout, URL of repository is https://svn.apache.org/repos/asf/openoffice/trunk/test/
== Run testing ==
'''As a normal user, how to run testing against an installed OpenOffice?''' 
Firstly compile the project with the command under test module.
ant -Dopenoffice.home="OpenOffice installation directory" compile
Then start testing with the command "run".
e.g. Run the given test classes
run -Dopenoffice.home="/Applications/OpenOffice.org.app/Contents" -tc pvt.gui.Benchmark

''' Where to get the testing result? '''

By default, the testing output is stored in "test/testspace/output***". Open "test/testspace/output/" in your browser to see the testing report. 

Special stuff in the output directory.
pvt.uno.Classname.xml:Test result in XML. Every case Every repeat's detail result
screenshot/: Screenshot pictures when test assert is failed.

==Sample on Windows==
Running Platform: Windows 7 64bit
*Install OO, use default install directory. "C:/Program Files (x86)/OpenOffice.org 4 "
*Checkout sourcecode to "C:\test"
*Change CMD directory to "C:\test",then compile test use: ant -Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4" compile
*Change CMD directory to "C:\test",then execute PVT: run -Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4 " -tc pvt.uno.Conversion

==FAQ==

{{Template:Documentation/Note| '''What is openoffice.home?''' 
The default installation directory of Apache OpenOffice: 
Mac OS X: "/Applications/OpenOffice.org.app/Contents" 
Linux: "/opt/openoffice.org4" 
Windows: "C:/Program Files/OpenOffice.org 4" 
Windows 64b: "C:\Program Files (x86)\OpenOffice 4"
}}
{{Template:Documentation/Note| '''Can I do other operations when PVT Gui is running?''' 
For PVT Gui cases wrote via GUI(Graphical User Interface) not UNO interface, little display offset may impact test result. So not do other operations when PVT is running.
}}
{{Template:Documentation/Note| '''Do I need compile pvt source code anytime?''' 
If there is not any change of pvt source code, there is no need to compile it anytime.
That is "Java is compile once, run everywhere"
}}

[[Category:Quality Assurance]]

QA/PVT Report

2013-09-05T10:18:23Z

Liupingtan: /* PVT_UNO report on 4.0.1_Dev_r1518667 */

==PVT_GUI report on 4.0.1_Dev_r1518667==
[[QA/AOO401_PVT_GUI_Result/r1518667_Windows7]]

[[Category:Quality Assurance]]

QA/PVT Report

2013-09-05T10:17:43Z

Liupingtan: /* PVT_UNO report on 4.0.1_Dev_r1518667 */

==PVT_UNO report on 4.0.1_Dev_r1518667==
[[QA/AOO401_PVT_GUI_Result/r1518667_Windows7]]

[[Category:Quality Assurance]]

QA/PVT

2013-09-01T01:06:24Z

Liupingtan: /* Run testing */

= Introduction =
Performance Verification Test, PVT for short, is a set of tests that run on new build to get the performance indicators of AOO. Performance indicators include consumed time/memory/handle after some operations. 
PVT of AOO consists of two parts: GUI and UNO. 
=== GUI PVT ===
GUI PVT is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation. 
=== UNO PVT ===
UNO PVT is to use UNO API to do basic documents operations, such as loading/saving/closing documents, then count the consumed time. 

You can view daily PVT report here: [http://people.apache.org/~liuzhe/testdashboard/#pvt] 

= Prerequisites =
==Platform==
Test machine with OS in below list:
WindowsXP, Windows7 32bit, Windows7 64bit,Ubuntu, Suse, Redhat,Mac

==AOO Build==
AOO4.0 [http://ci.apache.org/projects/openoffice/index.html build snapshots] 
AOO4.0.1 Development Build [https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds]

==Environment tools==
*SVN Client:
On Windows: Download and Install TortoiseSVN as SVN Client to checkout sourcecode. 
[http://tortoisesvn.net/downloads.html http://tortoisesvn.net/downloads.html] 
*JDK: [http://java.sun.com/javase/6/ JDK 1.6] or above. 
*Ant: [http://ant.apache.org/bindownload.cgi Apache Ant 1.8.2] or above.

==Soft Skills==
*Basic skills about Windows Command line, Linux/Mac Terminal
*Basic knowledge of Java

=How to run PVT automatically=
== Getting the source code ==
Anyone can checkout source code from our Subversion repository. Run the following command.
svn co https://svn.apache.org/repos/asf/openoffice/trunk/test/ test

On Windows, you can use TortoiseSVN GUI Client to checkout, URL of repository is https://svn.apache.org/repos/asf/openoffice/trunk/test/
== Run testing ==
'''As a normal user, how to run testing against an installed OpenOffice?''' 
Firstly compile the project with the command under test module.
ant -Dopenoffice.home="OpenOffice installation directory" compile
Then start testing with the command "run".
e.g. Run the given test classes
run -Dopenoffice.home="/Applications/OpenOffice.org.app/Contents" -tc pvt.uno.Conversion

''' Where to get the testing result? '''

By default, the testing output is stored in "test/testspace/output***". Open "test/testspace/output/" in your browser to see the testing report. 

Special stuff in the output directory.
pvt.uno.Classname.xml:Test result in XML. Every case Every repeat's detail result
screenshot/: Screenshot pictures when test assert is failed.

==Sample on Windows==
Running Platform: Windows 7 64bit
*Install OO, use default install directory. "C:/Program Files (x86)/OpenOffice.org 4 "
*Checkout sourcecode to "C:\test"
*Change CMD directory to "C:\test",then compile test use: ant -Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4" compile
*Change CMD directory to "C:\test",then execute PVT: run -Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4 " -tc pvt.uno.Conversion

==FAQ==

{{Template:Documentation/Note| '''What is openoffice.home?''' 
The default installation directory of Apache OpenOffice: 
Mac OS X: "/Applications/OpenOffice.org.app/Contents" 
Linux: "/opt/openoffice.org4" 
Windows: "C:/Program Files/OpenOffice.org 4" 
Windows 64b: "C:\Program Files (x86)\OpenOffice 4"
}}
{{Template:Documentation/Note| '''Can I do other operations when PVT Gui is running?''' 
For PVT Gui cases wrote via GUI(Graphical User Interface) not UNO interface, little display offset may impact test result. So not do other operations when PVT is running.
}}
{{Template:Documentation/Note| '''Do I need compile pvt source code anytime?''' 
If there is not any change of pvt source code, there is no need to compile it anytime.
That is "Java is compile once, run everywhere"
}}

QA/PVT Report

2013-09-01T00:06:00Z

Liupingtan: /* PVT_UNO report on 4.0.1_Dev_r1518667 */

==PVT_UNO report on 4.0.1_Dev_r1518667==
[[QA/AOO401_PVT_UNO_Result/r1518667_Windows7]]

QA/AOO401 PVT UNO Result/r1518667

2013-09-01T00:02:34Z

Liupingtan: Created page with " '''Test Environment:''' CPU:2.6 GHz; Mem: 8GB '''Test Build:''' AOO4.0.1_r1518667 '''Test Evaluation Method:''' Automatically run each test case 8 times and compute the av..."

'''Test Environment:''' CPU:2.6 GHz; Mem: 8GB

'''Test Build:''' AOO4.0.1_r1518667

'''Test Evaluation Method:''' Automatically run each test case 8 times
and compute the average value of 6 times (excluding the minimum and maximum result).

QA/PVT Report

2013-08-31T23:55:51Z

Liupingtan: Created page with " ==PVT_UNO report on 4.0.1_Dev_r1518667== QA/AOO401_PVT_UNO_Result/r1518667"

==PVT_UNO report on 4.0.1_Dev_r1518667==
[[QA/AOO401_PVT_UNO_Result/r1518667]]

Quality Assurance

2013-08-31T23:50:49Z

Liupingtan: /* Automation Test */

==General Information==
Quality Assurance (QA) is more than testing! 
You can find some interesting articles about [http://en.wikipedia.org/wiki/Software_quality Software Quality] and [http://en.wikipedia.org/wiki/Software_testing Software Testing] at [http://en.wikipedia.org/wiki/Main_Page WikiPedia].

The Apache OpenOffice community community members working on quality assurance [http://en.wikipedia.org/wiki/Software_quality_assurance (QA)] functions perform important actions for the group effort overall.

If you are interested in doing QA for OpenOffice.org, please feel free, and encouraged, to join the community. You can find all relevant information about joining the team at [http://qa.openoffice.org/ooQAReloaded/Docs/QA-Reloaded-HowToStart.html How-To-Start page].

==Helpful links ==
* Homepage of the QA project on OOo : http://openoffice.apache.org/qa.html
* Mailing list of the QA project:
:Subscribe: mailto:ooo-qa-subscribe@incubator.apache.org
:Archives [http://markmail.org/search/+list:org.apache.incubator.ooo-qa Markmail] [http://mail-archives.apache.org/mod_mbox/incubator-ooo-qa/ Apache]
* Query for existing bugs in IssueTracker : https://issues.apache.org/ooo/
* Writing a new issue in IssueTracker :
:[https://issues.apache.org/ooo/enter_bug.cgi Bugzilla New Issue]
:[[Issue_lifecycle]], a workflow for Bugzilla
* QA category on OOo wiki : [[:Category:Quality_Assurance|Quality Assurance]]
*[[QA/test_automation|Test Automation]]
*[[QA/Build Verification Test(BVT)|Buid Verification Test]]
*[[QA/Performance Verification Test(PVT)|Performance Verification Test]]
*[[Performance/AOO3.4.1_PVT_Introduction]]
*[[QA/SVT | System Verification Test(SVT)]]
*[[QA/SVTReport | SVT/SVT Report]]
*[[QA/AOO341_TestCase/Installation |Installation test cases]]

==Issue Tracking ==
*[[Issue_lifecycle]], a workflow for Bugzilla
*[[QA/HowToFileIssue]], a guide for how to open defect in Bugzilla

==Test Case==
'''[http://aootesting.adfinis-sygroup.org/index.php Tool Testlink] is used for test case management:'''
*[[QA/Testcase/How_to_write_test_case |a guide for how to write a test case]],
*[[QA/Testcase/Template |template for test case]],
*[[QA/Testcase/Sample |a sample test case]],
*[[QA/Testlink |a guide for test management]].
*[[QA/Tescase |Database Test Matrix]].
*[[QA/Testcase|General Testing]].

==Automation Test==
* Automation Guide
**[[QA/test_automation_guide|Automation Usage Guide]]
**[[QA/dev_gui_testing | Automation Development Guide]]
**[[QA/vclauto/A_step_by_step_example | GUI Case Development Step by Step Example]]
* BVT(Buid Verification Test)
**[[QA/Build Verification Test(BVT)|Buid Verification Test]]
**[[http://wiki.openoffice.org/wiki/QA/BVT How to run BVT]]
**[[http://wiki.openoffice.org/wiki/QA/BVT_Report BVT Report]]
* PVT(Performance Verification Test)
**[[QA/Performance Verification Test(PVT)|Performance Verification Test]]
**[[Performance/AOO3.4.1_PVT_Introduction]]
**[[http://wiki.openoffice.org/wiki/QA/PVT How to run PVT]]
**[[http://wiki.openoffice.org/wiki/QA/PVT_Report PVT Report]]
* SVT(System Verification Test)
**[[QA/SVT | System Verification Test]]
**[[QA/SVTReport | SVT/SVT Report]]
* FVT(Function Verification Test)
*Automation Todos
**[[QA/FVT/FVTRefactor | FVT Case Refactor]]
**[[QA/Auto/TodoList | Todo WorkList]]

==Routine Test Report==

* [http://people.apache.org/~liuzhe/testdashboard/#bvt Daily Build Verification Test Report]
* [http://people.apache.org/~liuzhe/testdashboard/#pvt Daily Performance Verification Test Report]
* [[QA/Report/FVT |Function Verification Test(FVT)]]
* [[QA/Report/WeeklyReport |Weekly Report]]
* [[QA/Report/DefectStatus |Defect Status Report]]

==Release testing==
===Apache OpenOffice 3.4===
If you have interesting in Apache OpenOffice 3.4 release and plan contribute your QA effort to it, please go to below links for test cases update and testing resul update.
* [http://ci.apache.org/projects/openoffice/install/ AOO 3.4 latest build]:
* [https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots AOO 3.4 Dev Snapshots build]:
* [https://cwiki.apache.org/confluence/display/OOOUSERS/Release-QA-Plan AOO 3.4 test plan]:
* [http://wiki.services.openoffice.org/wiki/QA/TestCases/ AOO 3.4 test cases (in multiple languages)]:
* [http://wiki.services.openoffice.org/wiki/QA/TestResults AOO 3.4 test results]:
* [https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+RC+Build+Test+Plan AOO 3.4 RC Build test plan]
* [https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+RC+Build+Test+Report AOO 3.4 RC Build test result]

===Apache OpenOffice 3.4.1===
If you are interested in Apache OpenOffice 3.4.1 release and plan to contribute your effort on QA work, please go to below link for test case update and test result update
* [https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-AOO3.4.1 AOO 3.4.1 dev snapshot build]:
* [https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4.1+Testing+Plan AOO 3.4.1 testing plan]
* [http://wiki.services.openoffice.org/wiki/QA/AOO341_TestCase AOO 3.4.1 test case]
* [http://wiki.services.openoffice.org/wiki/QA/AOO341_TestResult AOO 3.4.1 test result]

:* [http://wiki.services.openoffice.org/wiki/QA/AOO341_GeneralTestingSummary AOO 3.4.1 general testing summary]
:* [http://wiki.services.openoffice.org/wiki/QA/AOO341_InstallationTestingSummary AOO 3.4.1 installation testing summary]

* [https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4.1+RC+Build+Test+Plan AOO 3.4.1 RC build test plan]
* [http://wiki.services.openoffice.org/wiki/QA/AOO341_RC_TestResult AOO 3.4.1 RC build test result]

[[Category:Quality Assurance]]

===Apache OpenOffice 4.0===
* [http://wiki.services.openoffice.org/wiki/QA/AOO40_Database Database General Test]
* [http://wiki.services.openoffice.org/wiki/QA/AOO40_Drawing Drawing General Test]

QA/PVT

2013-08-31T23:49:25Z

Liupingtan: /* Sample on Windows */

= Introduction =
Performance Verification Test, PVT for short, is a set of tests that run on new build to get the performance indicators of AOO. Performance indicators include consumed time/memory/handle after some operations. 
PVT of AOO consists of two parts: GUI and UNO. 
=== GUI PVT ===
GUI PVT is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation. 
=== UNO PVT ===
UNO PVT is to use UNO API to do basic documents operations, such as loading/saving/closing documents, then count the consumed time. 

You can view daily PVT report here: [http://people.apache.org/~liuzhe/testdashboard/#pvt] 

= Prerequisites =
==Platform==
Test machine with OS in below list:
WindowsXP, Windows7 32bit, Windows7 64bit,Ubuntu, Suse, Redhat,Mac

==AOO Build==
AOO4.0 [http://ci.apache.org/projects/openoffice/index.html build snapshots] 
AOO4.0.1 Development Build [https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds]

==Environment tools==
*SVN Client:
On Windows: Download and Install TortoiseSVN as SVN Client to checkout sourcecode. 
[http://tortoisesvn.net/downloads.html http://tortoisesvn.net/downloads.html] 
*JDK: [http://java.sun.com/javase/6/ JDK 1.6] or above. 
*Ant: [http://ant.apache.org/bindownload.cgi Apache Ant 1.8.2] or above.

==Soft Skills==
*Basic skills about Windows Command line, Linux/Mac Terminal
*Basic knowledge of Java

=How to run PVT automatically=
== Getting the source code ==
Anyone can checkout source code from our Subversion repository. Run the following command.
svn co https://svn.apache.org/repos/asf/openoffice/trunk/test/ test

On Windows, you can use TortoiseSVN GUI Client to checkout, URL of repository is https://svn.apache.org/repos/asf/openoffice/trunk/test/
== Run testing ==
'''As a normal user, how to run testing against an installed OpenOffice?''' 
Firstly compile the project with the command under test module.
ant -Dopenoffice.home="OpenOffice installation directory" compile
Then start testing with the command "run".
e.g. Run the given test classes
run -Dopenoffice.home="/Applications/OpenOffice.org.app/Contents" -tc pvt.uno.Conversion

''' Where to get the testing result? '''

By default, the testing output is stored in "test/testspace/output***". Open "test/testspace/output/" in your browser to see the testing report. 

Special stuff in the output directory.
result.xml: Test result in XML. Every case's detail result
result.html: Test result in HTML. Collect all case's result, to report as HTML.Ň
screenshot/: Screenshot pictures when test assert is failed.

==Sample on Windows==
Running Platform: Windows 7 64bit
*Install OO, use default install directory. "C:/Program Files (x86)/OpenOffice.org 4 "
*Checkout sourcecode to "C:\test"
*Change CMD directory to "C:\test",then compile test use: ant -Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4" compile
*Change CMD directory to "C:\test",then execute PVT: run -Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4 " -tc pvt.uno.Conversion

==FAQ==

{{Template:Documentation/Note| '''What is openoffice.home?''' 
The default installation directory of Apache OpenOffice: 
Mac OS X: "/Applications/OpenOffice.org.app/Contents" 
Linux: "/opt/openoffice.org4" 
Windows: "C:/Program Files/OpenOffice.org 4" 
Windows 64b: "C:\Program Files (x86)\OpenOffice 4"
}}
{{Template:Documentation/Note| '''Can I do other operations when PVT Gui is running?''' 
For PVT Gui cases wrote via GUI(Graphical User Interface) not UNO interface, little display offset may impact test result. So not do other operations when PVT is running.
}}
{{Template:Documentation/Note| '''Do I need compile pvt source code anytime?''' 
If there is not any change of pvt source code, there is no need to compile it anytime.
That is "Java is compile once, run everywhere"
}}

QA/PVT

2013-08-31T23:46:06Z

Liupingtan: /* FAQ */

= Introduction =
Performance Verification Test, PVT for short, is a set of tests that run on new build to get the performance indicators of AOO. Performance indicators include consumed time/memory/handle after some operations. 
PVT of AOO consists of two parts: GUI and UNO. 
=== GUI PVT ===
GUI PVT is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation. 
=== UNO PVT ===
UNO PVT is to use UNO API to do basic documents operations, such as loading/saving/closing documents, then count the consumed time. 

You can view daily PVT report here: [http://people.apache.org/~liuzhe/testdashboard/#pvt] 

= Prerequisites =
==Platform==
Test machine with OS in below list:
WindowsXP, Windows7 32bit, Windows7 64bit,Ubuntu, Suse, Redhat,Mac

==AOO Build==
AOO4.0 [http://ci.apache.org/projects/openoffice/index.html build snapshots] 
AOO4.0.1 Development Build [https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds]

==Environment tools==
*SVN Client:
On Windows: Download and Install TortoiseSVN as SVN Client to checkout sourcecode. 
[http://tortoisesvn.net/downloads.html http://tortoisesvn.net/downloads.html] 
*JDK: [http://java.sun.com/javase/6/ JDK 1.6] or above. 
*Ant: [http://ant.apache.org/bindownload.cgi Apache Ant 1.8.2] or above.

==Soft Skills==
*Basic skills about Windows Command line, Linux/Mac Terminal
*Basic knowledge of Java

=How to run PVT automatically=
== Getting the source code ==
Anyone can checkout source code from our Subversion repository. Run the following command.
svn co https://svn.apache.org/repos/asf/openoffice/trunk/test/ test

On Windows, you can use TortoiseSVN GUI Client to checkout, URL of repository is https://svn.apache.org/repos/asf/openoffice/trunk/test/
== Run testing ==
'''As a normal user, how to run testing against an installed OpenOffice?''' 
Firstly compile the project with the command under test module.
ant -Dopenoffice.home="OpenOffice installation directory" compile
Then start testing with the command "run".
e.g. Run the given test classes
run -Dopenoffice.home="/Applications/OpenOffice.org.app/Contents" -tc pvt.uno.Conversion

''' Where to get the testing result? '''

By default, the testing output is stored in "test/testspace/output***". Open "test/testspace/output/" in your browser to see the testing report. 

Special stuff in the output directory.
result.xml: Test result in XML. Every case's detail result
result.html: Test result in HTML. Collect all case's result, to report as HTML.Ň
screenshot/: Screenshot pictures when test assert is failed.

==Sample on Windows==
Running Platform: Windows 7 64bit
*Install OO, use default install directory. "C:/Program Files (x86)/OpenOffice.org 4 "
*Checkout sourcecode to "C:\test"
*Change CMD directory to "C:\test",then compile test use: ant -Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4" compile
*Change CMD directory to "C:\test",then execute BVT: run -Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4 " -tc pvt.uno.Conversion

==FAQ==

{{Template:Documentation/Note| '''What is openoffice.home?''' 
The default installation directory of Apache OpenOffice: 
Mac OS X: "/Applications/OpenOffice.org.app/Contents" 
Linux: "/opt/openoffice.org4" 
Windows: "C:/Program Files/OpenOffice.org 4" 
Windows 64b: "C:\Program Files (x86)\OpenOffice 4"
}}
{{Template:Documentation/Note| '''Can I do other operations when PVT Gui is running?''' 
For PVT Gui cases wrote via GUI(Graphical User Interface) not UNO interface, little display offset may impact test result. So not do other operations when PVT is running.
}}
{{Template:Documentation/Note| '''Do I need compile pvt source code anytime?''' 
If there is not any change of pvt source code, there is no need to compile it anytime.
That is "Java is compile once, run everywhere"
}}

QA/PVT

2013-08-31T23:45:35Z

Liupingtan: /* FAQ */

= Introduction =
Performance Verification Test, PVT for short, is a set of tests that run on new build to get the performance indicators of AOO. Performance indicators include consumed time/memory/handle after some operations. 
PVT of AOO consists of two parts: GUI and UNO. 
=== GUI PVT ===
GUI PVT is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation. 
=== UNO PVT ===
UNO PVT is to use UNO API to do basic documents operations, such as loading/saving/closing documents, then count the consumed time. 

You can view daily PVT report here: [http://people.apache.org/~liuzhe/testdashboard/#pvt] 

= Prerequisites =
==Platform==
Test machine with OS in below list:
WindowsXP, Windows7 32bit, Windows7 64bit,Ubuntu, Suse, Redhat,Mac

==AOO Build==
AOO4.0 [http://ci.apache.org/projects/openoffice/index.html build snapshots] 
AOO4.0.1 Development Build [https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds]

==Environment tools==
*SVN Client:
On Windows: Download and Install TortoiseSVN as SVN Client to checkout sourcecode. 
[http://tortoisesvn.net/downloads.html http://tortoisesvn.net/downloads.html] 
*JDK: [http://java.sun.com/javase/6/ JDK 1.6] or above. 
*Ant: [http://ant.apache.org/bindownload.cgi Apache Ant 1.8.2] or above.

==Soft Skills==
*Basic skills about Windows Command line, Linux/Mac Terminal
*Basic knowledge of Java

=How to run PVT automatically=
== Getting the source code ==
Anyone can checkout source code from our Subversion repository. Run the following command.
svn co https://svn.apache.org/repos/asf/openoffice/trunk/test/ test

On Windows, you can use TortoiseSVN GUI Client to checkout, URL of repository is https://svn.apache.org/repos/asf/openoffice/trunk/test/
== Run testing ==
'''As a normal user, how to run testing against an installed OpenOffice?''' 
Firstly compile the project with the command under test module.
ant -Dopenoffice.home="OpenOffice installation directory" compile
Then start testing with the command "run".
e.g. Run the given test classes
run -Dopenoffice.home="/Applications/OpenOffice.org.app/Contents" -tc pvt.uno.Conversion

''' Where to get the testing result? '''

By default, the testing output is stored in "test/testspace/output***". Open "test/testspace/output/" in your browser to see the testing report. 

Special stuff in the output directory.
result.xml: Test result in XML. Every case's detail result
result.html: Test result in HTML. Collect all case's result, to report as HTML.Ň
screenshot/: Screenshot pictures when test assert is failed.

==Sample on Windows==
Running Platform: Windows 7 64bit
*Install OO, use default install directory. "C:/Program Files (x86)/OpenOffice.org 4 "
*Checkout sourcecode to "C:\test"
*Change CMD directory to "C:\test",then compile test use: ant -Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4" compile
*Change CMD directory to "C:\test",then execute BVT: run -Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4 " -tc pvt.uno.Conversion

==FAQ==

{{Template:Documentation/Note| '''What is openoffice.home?''' 
The default installation directory of Apache OpenOffice: 
Mac OS X: "/Applications/OpenOffice.org.app/Contents" 
Linux: "/opt/openoffice.org4" 
Windows: "C:/Program Files/OpenOffice.org 4" 
Windows 64b: "C:\Program Files (x86)\OpenOffice 4"
}}
{{Template:Documentation/Note| '''Can I do other operations when PVT Gui is running?''' 
For PVT Gui cases wrote via GUI(Graphical User Interface) not UNO interface, little display offset may impact test result. So not do other operations
when PVT is running.
}}
{{Template:Documentation/Note| '''Do I need compile pvt source code anytime?''' 
If there is not any change of pvt source code, there is no need to compile it anytime.
That is "Java is compile once, run everywhere"
}}

QA/PVT

2013-08-31T23:43:53Z

Liupingtan: /* Sample on Windows */

= Introduction =
Performance Verification Test, PVT for short, is a set of tests that run on new build to get the performance indicators of AOO. Performance indicators include consumed time/memory/handle after some operations. 
PVT of AOO consists of two parts: GUI and UNO. 
=== GUI PVT ===
GUI PVT is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation. 
=== UNO PVT ===
UNO PVT is to use UNO API to do basic documents operations, such as loading/saving/closing documents, then count the consumed time. 

You can view daily PVT report here: [http://people.apache.org/~liuzhe/testdashboard/#pvt] 

= Prerequisites =
==Platform==
Test machine with OS in below list:
WindowsXP, Windows7 32bit, Windows7 64bit,Ubuntu, Suse, Redhat,Mac

==AOO Build==
AOO4.0 [http://ci.apache.org/projects/openoffice/index.html build snapshots] 
AOO4.0.1 Development Build [https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds]

==Environment tools==
*SVN Client:
On Windows: Download and Install TortoiseSVN as SVN Client to checkout sourcecode. 
[http://tortoisesvn.net/downloads.html http://tortoisesvn.net/downloads.html] 
*JDK: [http://java.sun.com/javase/6/ JDK 1.6] or above. 
*Ant: [http://ant.apache.org/bindownload.cgi Apache Ant 1.8.2] or above.

==Soft Skills==
*Basic skills about Windows Command line, Linux/Mac Terminal
*Basic knowledge of Java

=How to run PVT automatically=
== Getting the source code ==
Anyone can checkout source code from our Subversion repository. Run the following command.
svn co https://svn.apache.org/repos/asf/openoffice/trunk/test/ test

On Windows, you can use TortoiseSVN GUI Client to checkout, URL of repository is https://svn.apache.org/repos/asf/openoffice/trunk/test/
== Run testing ==
'''As a normal user, how to run testing against an installed OpenOffice?''' 
Firstly compile the project with the command under test module.
ant -Dopenoffice.home="OpenOffice installation directory" compile
Then start testing with the command "run".
e.g. Run the given test classes
run -Dopenoffice.home="/Applications/OpenOffice.org.app/Contents" -tc pvt.uno.Conversion

''' Where to get the testing result? '''

By default, the testing output is stored in "test/testspace/output***". Open "test/testspace/output/" in your browser to see the testing report. 

Special stuff in the output directory.
result.xml: Test result in XML. Every case's detail result
result.html: Test result in HTML. Collect all case's result, to report as HTML.Ň
screenshot/: Screenshot pictures when test assert is failed.

==Sample on Windows==
Running Platform: Windows 7 64bit
*Install OO, use default install directory. "C:/Program Files (x86)/OpenOffice.org 4 "
*Checkout sourcecode to "C:\test"
*Change CMD directory to "C:\test",then compile test use: ant -Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4" compile
*Change CMD directory to "C:\test",then execute BVT: run -Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4 " -tc pvt.uno.Conversion

==FAQ==

{{Template:Documentation/Note| '''What is openoffice.home?''' 
The default installation directory of Apache OpenOffice: 
Mac OS X: "/Applications/OpenOffice.org.app/Contents" 
Linux: "/opt/openoffice.org4" 
Windows: "C:/Program Files/OpenOffice.org 4" 
Windows 64b: "C:\Program Files (x86)\OpenOffice 4"
}}
{{Template:Documentation/Note| '''Can I do other operations when PVT Gui is running?''' 
For
PVT Gui cases wrote via GUI(Graphical User Interface) not UNO interface,
little display offset may impact test result. So not do other operations
when PVT is running.
}}
{{Template:Documentation/Note| '''Do I need compile pvt source code anytime?''' 
If there is not any change of pvt source code, there is no need to compile it anytime.
That is "Java is compile once, run everywhere"
}}

QA/PVT

2013-08-31T23:39:21Z

Liupingtan:

= Introduction =
Performance Verification Test, PVT for short, is a set of tests that run on new build to get the performance indicators of AOO. Performance indicators include consumed time/memory/handle after some operations. 
PVT of AOO consists of two parts: GUI and UNO. 
=== GUI PVT ===
GUI PVT is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation. 
=== UNO PVT ===
UNO PVT is to use UNO API to do basic documents operations, such as loading/saving/closing documents, then count the consumed time. 

You can view daily PVT report here: [http://people.apache.org/~liuzhe/testdashboard/#pvt] 

= Prerequisites =
==Platform==
Test machine with OS in below list:
WindowsXP, Windows7 32bit, Windows7 64bit,Ubuntu, Suse, Redhat,Mac

==AOO Build==
AOO4.0 [http://ci.apache.org/projects/openoffice/index.html build snapshots] 
AOO4.0.1 Development Build [https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds]

==Environment tools==
*SVN Client:
On Windows: Download and Install TortoiseSVN as SVN Client to checkout sourcecode. 
[http://tortoisesvn.net/downloads.html http://tortoisesvn.net/downloads.html] 
*JDK: [http://java.sun.com/javase/6/ JDK 1.6] or above. 
*Ant: [http://ant.apache.org/bindownload.cgi Apache Ant 1.8.2] or above.

==Soft Skills==
*Basic skills about Windows Command line, Linux/Mac Terminal
*Basic knowledge of Java

=How to run PVT automatically=
== Getting the source code ==
Anyone can checkout source code from our Subversion repository. Run the following command.
svn co https://svn.apache.org/repos/asf/openoffice/trunk/test/ test

On Windows, you can use TortoiseSVN GUI Client to checkout, URL of repository is https://svn.apache.org/repos/asf/openoffice/trunk/test/
== Run testing ==
'''As a normal user, how to run testing against an installed OpenOffice?''' 
Firstly compile the project with the command under test module.
ant -Dopenoffice.home="OpenOffice installation directory" compile
Then start testing with the command "run".
e.g. Run the given test classes
run -Dopenoffice.home="/Applications/OpenOffice.org.app/Contents" -tc pvt.uno.Conversion

''' Where to get the testing result? '''

By default, the testing output is stored in "test/testspace/output***". Open "test/testspace/output/" in your browser to see the testing report. 

Special stuff in the output directory.
result.xml: Test result in XML. Every case's detail result
result.html: Test result in HTML. Collect all case's result, to report as HTML.Ň
screenshot/: Screenshot pictures when test assert is failed.

==Sample on Windows==
Running Platform: Windows 7 64bit
*Install OO, use default install directory. "C:/Program Files (x86)/OpenOffice.org 4 "
*Checkout sourcecode to "C:\test"
*Change
CMD directory to "C:\test",then compile test use: ant
-Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4" compile
*Change CMD directory to "C:\test",then execute BVT: run -Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4 " -tc pvt.uno.Conversion

==FAQ==

{{Template:Documentation/Note| '''What is openoffice.home?''' 
The default installation directory of Apache OpenOffice: 
Mac OS X: "/Applications/OpenOffice.org.app/Contents" 
Linux: "/opt/openoffice.org4" 
Windows: "C:/Program Files/OpenOffice.org 4" 
Windows 64b: "C:\Program Files (x86)\OpenOffice 4"
}}
{{Template:Documentation/Note| '''Can I do other operations when PVT Gui is running?''' 
For
PVT Gui cases wrote via GUI(Graphical User Interface) not UNO interface,
little display offset may impact test result. So not do other operations
when PVT is running.
}}
{{Template:Documentation/Note| '''Do I need compile pvt source code anytime?''' 
If there is not any change of pvt source code, there is no need to compile it anytime.
That is "Java is compile once, run everywhere"
}}

QA/PVT

2013-08-31T23:36:53Z

Liupingtan:

= Introduction =
Performance Verification Test, PVT for short, is a set of tests that run on new build to get the performance indicators of AOO. Performance indicators include consumed time/memory/handle after some operations. 
PVT of AOO consists of two parts: GUI and UNO. 
=== GUI PVT ===
GUI PVT is to simulate a common user to perform basic but core operations of each editor and count the consumed time/memory/handle after each operation. 
=== UNO PVT ===
UNO PVT is to use UNO API to do basic documents operations, such as loading/saving/closing documents, then count the consumed time. 

You can view daily PVT report here: [http://people.apache.org/~liuzhe/testdashboard/#pvt] 

==Platform==
Test machine with OS in below list:
WindowsXP, Windows7 32bit, Windows7 64bit,Ubuntu, Suse, Redhat,Mac

==AOO Build==
AOO4.0 [http://ci.apache.org/projects/openoffice/index.html build snapshots] 
AOO4.0.1 Development Build [https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds]

==Environment tools==
*SVN Client:
On Windows: Download and Install TortoiseSVN as SVN Client to checkout sourcecode. 
[http://tortoisesvn.net/downloads.html http://tortoisesvn.net/downloads.html] 
*JDK: [http://java.sun.com/javase/6/ JDK 1.6] or above. 
*Ant: [http://ant.apache.org/bindownload.cgi Apache Ant 1.8.2] or above.

==Soft Skills==
*Basic skills about Windows Command line, Linux/Mac Terminal
*Basic knowledge of Java

=How to run PVT automatically=
== Getting the source code ==
Anyone can checkout source code from our Subversion repository. Run the following command.
svn co https://svn.apache.org/repos/asf/openoffice/trunk/test/ test

On Windows, you can use TortoiseSVN GUI Client to checkout, URL of repository is https://svn.apache.org/repos/asf/openoffice/trunk/test/
== Run testing ==
'''As a normal user, how to run testing against an installed OpenOffice?''' 
Firstly compile the project with the command under test module.
ant -Dopenoffice.home="OpenOffice installation directory" compile
Then start testing with the command "run".
e.g. Run the given test classes
run -Dopenoffice.home="/Applications/OpenOffice.org.app/Contents" -tc pvt.uno.Conversion

''' Where to get the testing result? '''

By default, the testing output is stored in "test/testspace/output***". Open "test/testspace/output/" in your browser to see the testing report. 

Special stuff in the output directory.
result.xml: Test result in XML. Every case's detail result
result.html: Test result in HTML. Collect all case's result, to report as HTML.Ň
screenshot/: Screenshot pictures when test assert is failed.

==Sample on Windows==
Running Platform: Windows 7 64bit
*Install OO, use default install directory. "C:/Program Files (x86)/OpenOffice.org 4 "
*Checkout sourcecode to "C:\test"
*Change
CMD directory to "C:\test",then compile test use: ant
-Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4" compile
*Change CMD directory to "C:\test",then execute BVT: run -Dopenoffice.home="C:/Program Files (x86)/OpenOffice.org 4 " -tc pvt.uno.Conversion

==FAQ==

{{Template:Documentation/Note| '''What is openoffice.home?''' 
The default installation directory of Apache OpenOffice: 
Mac OS X: "/Applications/OpenOffice.org.app/Contents" 
Linux: "/opt/openoffice.org4" 
Windows: "C:/Program Files/OpenOffice.org 4" 
Windows 64b: "C:\Program Files (x86)\OpenOffice 4"
}}
{{Template:Documentation/Note| '''Can I do other operations when PVT Gui is running?''' 
For
PVT Gui cases wrote via GUI(Graphical User Interface) not UNO interface,
little display offset may impact test result. So not do other operations
when PVT is running.
}}
{{Template:Documentation/Note| '''Do I need compile pvt source code anytime?''' 
If there is not any change of pvt source code, there is no need to compile it anytime.
That is "Java is compile once, run everywhere"
}}