Release QA for localized OOo with VCL testtool
From Apache OpenOffice Wiki
Contents
Introduction
The development cycle of OpenOffice.org(OOo), the release engineering team, and other volunteers provide release candidates. For example OOo 2.1, 2.1RC1 and RC2... To mark as `released', release candidate packages must be QA'ed. How candidates are QA'ed are up-to the responsibilities of QA lead of each native language project or porting team. A possible release test can be done by using VCL testtool, and it is widely accepted.
Using VMware Player
For Pentium 4/Athlon/Opteron machines, we used VMware Player which is freely available. http://www.vmware.com/products/player/ In this document, we intensively used VMware Player. Pros and Cons are following:
Pros:
- Fast!
- We can isolate environments so that do not change settings for QA test.
- We can perform clean tests. Some other installed software affect your tests.
- Usually we can perform two tests at the same time, because VCL test doesn't consume much CPU resources.
Cons:
- Creating virtual alliances are bit tedious. Need qemu http://fabrice.bellard.free.fr/qemu/ , windows version is also available: http://www.h7.dion.ne.jp/~qemu-win/index.html
- VMware tools is not comes with VMware player. Can take from VMware server (also freely available)
How long does one release test take?
- Release sanity test usually takes about 15 hours regardless of the platform, e.g., CPU etc.
- Full test (usuanlly not recommended) takes 3 days.
Available documents
On this Wiki also have a look in the same category Quality Assurance.
