Release QA for localized OOo with VCL testtool

From Apache OpenOffice Wiki
Revision as of 10:55, 29 August 2022 by DiGro (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Book-old.png    This article is outdated.    


The development cycle of, the release engineering team, and other volunteers provide release candidates. For example OOo 2.1, they provide 2.1RC1 (release candidate 1) and RC2 (release candidate 2)... To mark as `released', release candidate packages must be QA'ed. How candidates are QA'ed, what test should be done 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, to perform ooo_release sanity test. This method is widely accepted.

Using VMware Player

QA for For Pentium 4/Athlon/Opteron packages, we recommend you to use VMware Player which is freely available for Windows and GNU/Linux. In this document, we intensively used VMware Player. Pros and Cons are following:


  • Fast!
  • We can isolate environments so that do not change settings for QA test.
  • We can perform clean tests. Some other installed software, and older settings affect your tests.
  • Usually we can perform two tests at the same time, because VCL test doesn't consume much CPU resources.
  • Drag and Drop between host-guest machine. Very easy to copy result files from guest OS.


  • Creating virtual alliances are bit tedious. Need qemu , windows version is also available:
  • VMware tools is not comes with VMware player. Can take from VMware server (also freely available)
  • VMware is just inside the virtual machine. Tests are NOT done in REAL machine. There must be some difference between two. We believe the difference does not affect vcl test.

Of course, you can use VMware Server. VMwaretools are there but bit slower. Which to choose is a personal preference.

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 necessary) takes 3 days.

Available documents

On this Wiki also have a look in the same category Quality Assurance.

Personal tools