Difference between revisions of "QA/Performance Verification Test(PVT)"
From Apache OpenOffice Wiki
< QA
(→UNO PVT) |
m (→UNO PVT) |
||
| Line 7: | Line 7: | ||
UNO PVT is to use UNO API to do basic documents operations, such as loading/saving/closing documents, then count the consumed time.<br /> | 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: [ | + | You can view daily PVT report here: [https://people.apache.org/~liuzhe/testdashboard/#pvt]<br /> |
[[Category:Quality Assurance]] | [[Category:Quality Assurance]] | ||
Latest revision as of 12:41, 27 October 2021
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]
