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

From Apache OpenOffice Wiki
Jump to: navigation, search
m (another layout)
Line 1: Line 1:
==== How to use QA testtool ====
+
==== How to use the VCL Testtool ====
 
by NAKATA, Maho (maho@openoffice.org) http://qa.openoffice.org/
 
by NAKATA, Maho (maho@openoffice.org) http://qa.openoffice.org/
  
Line 11: Line 11:
 
  * You can VMware server, too but this is a persona pereference; but VMware player is bit faster.
 
  * You can VMware server, too but this is a persona pereference; but VMware player is bit faster.
  
=== How long does one QAtest take? ===
+
=== How long does one test run take? ===
Release sanity test usually takes about 15hours regardless of the platform, e.g., CPU etc.
+
Release sanity test usually takes about 15 hours regardless of the platform, e.g., CPU etc.
  
 
=== Available documents ===
 
=== Available documents ===
  
Windows XP :http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7469
+
* On this Wiki also have a look in the same category ''Quality Assurance''.
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
+
* [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)]
 
+
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7490 Solaris 10 (x86)]
Solaris 10 (i386) : http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7491
+
* [http://wiki.services.openoffice.org/wiki/Testtool_FD6_en Fedora Core 6]
Solaris 10 (1386) : http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7490
+
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7495 Fedora Core 6]
Fedora Core 6 : http://wiki.services.openoffice.org/wiki/Testtool_FD6_en
+
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7672 MacOSX PowerPC]
Fedora Core 6 : http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7495
+
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7553 MacOSX Intel]
MacOSX PPC  : http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7672
+
MacOSX Intel : http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7553
+
  
 
[[Category:Quality Assurance]]
 
[[Category:Quality Assurance]]

Revision as of 07:43, 11 January 2007

How to use the VCL Testtool

by NAKATA, Maho (maho@openoffice.org) http://qa.openoffice.org/

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.

VMplayer or not?

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?

Release sanity test usually takes about 15 hours regardless of the platform, e.g., CPU etc.

Available documents

Personal tools