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

From Apache OpenOffice Wiki
Jump to: navigation, search
(→‎Available documents)
(→‎Available documents)
Line 26: Line 26:
 
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''.
 
* [[Testtool WinXP en|Windows XP]]
 
* [[Testtool WinXP en|Windows XP]]
−
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7469 Windows XP]
+
* [[|Windows 2000]
−
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7433 Windows 2000]
+
 
* [[QA_using_VCLtesttool_for_Solaris10_i386|Solaris10 (x86)]]
 
* [[QA_using_VCLtesttool_for_Solaris10_i386|Solaris10 (x86)]]
−
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7491 Solaris 10 (x86)]
 
−
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7490 Solaris 10 (x86)]
 
 
* [[Testtool FD6 en|Fedora Core 6]]
 
* [[Testtool FD6 en|Fedora Core 6]]
−
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7495 Fedora Core 6]
+
* [[VCL_testtool_MacOSX_PPC |MacOSX PowerPC]]
−
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7672 MacOSX PowerPC]
+
* [[VCL_testtool_MacOSX_Intel|MacOSX Intel]]
−
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7553 MacOSX Intel]
+
  
 
[[Category:Quality Assurance]]
 
[[Category:Quality Assurance]]

Revision as of 02:20, 12 January 2007


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:

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.

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