Difference between revisions of "QA/Performance Verification Test(PVT)"
From Apache OpenOffice Wiki
< QA
(→Introduction) |
(→UNO PVT) |
||
Line 5: | Line 5: | ||
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.<br /> | 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.<br /> | ||
=== UNO PVT === | === UNO PVT === | ||
− | UNO PVT is to use UNO API to do basic documents operations, such as loading | + | UNO PVT is to use UNO API to do basic documents operations, such as loading/saving/closing documents, then count the consumed time.<br /> |
You can view daily PVT report here: [http://people.apache.org/~liuzhe/testdashboard/#pvt]<br /> | You can view daily PVT report here: [http://people.apache.org/~liuzhe/testdashboard/#pvt]<br /> | ||
[[Category:Quality Assurance]] | [[Category:Quality Assurance]] |
Revision as of 03:42, 17 October 2012
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: [1]