Difference between revisions of "Release QA for localized OOo with VCL testtool"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (another layout)
(24 intermediate revisions by 5 users not shown)
Line 1: Line 1:
−
==== How to use the VCL Testtool ====
 
−
by NAKATA, Maho (maho@openoffice.org) http://qa.openoffice.org/
 
−
 
 
=== Introduction ===
 
=== Introduction ===
−
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. A possible release test can be done by using QAtesttool, and it is widely accepted.
+
The development cycle of OpenOffice.org(OOo), 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, http://qa.openoffice.org/qatesttool/index.html 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.  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, 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.
 +
 
 +
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)
 +
* 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.
  
−
=== VMplayer or not? ===
+
Of course, you can use VMware Server. VMwaretools are there but bit slower. Which to choose is a personal preference.
−
For Pentium/Opteron machines, we used VMware player which is freely available and in this document, we used intensively used VMware player (or vmware server)
+
−
* We can isolate OpenOffice.org environment and do not break ones setting for tests
+
−
* We can perform two tests at the same time.
+
−
* You can VMware server, too but this is a persona pereference; but VMware player is bit faster.
+
  
−
=== How long does one test run take? ===
+
=== How long does one release test take? ===
−
Release sanity test usually takes about 15 hours regardless of the platform, e.g., CPU etc.
+
* 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 ===
 
=== Available documents ===
  
−
* On this Wiki also have a look in the same category ''Quality Assurance''.
+
On this Wiki also have a look in the same category ''Quality Assurance''.
−
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7469 Windows XP]
+
* [[Testtool WinXP en|Windows XP]]
−
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7433 Windows 2000]
+
* [[|Windows 2000]
−
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7491 Solaris 10 (x86)]
+
* [[QA_using_VCLtesttool_for_Solaris10_i386|Solaris10 (x86)]]
−
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7490 Solaris 10 (x86)]
+
* [[Testtool FD6 en|Fedora Core 6]]
−
* [http://wiki.services.openoffice.org/wiki/Testtool_FD6_en Fedora Core 6]
+
* [[VCL_testtool_MacOSX_PPC |MacOSX PowerPC]]
−
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7495 Fedora Core 6]
+
* [[VCL_testtool_MacOSX_Intel|MacOSX Intel]]
−
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7672 MacOSX PowerPC]
+
−
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7553 MacOSX Intel]
+
  
 
[[Category:Quality Assurance]]
 
[[Category:Quality Assurance]]
 +
[[Category:Localization]]

Revision as of 10:51, 3 April 2008

Introduction

The development cycle of OpenOffice.org(OOo), 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, http://qa.openoffice.org/qatesttool/index.html 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. 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, 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.

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)
  • 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.

Retrieved from "https://wiki.openoffice.org/w/index.php?title=Release_QA_for_localized_OOo_with_VCL_testtool&oldid=72477"
Personal tools