Difference between revisions of "Release QA for localized OOo with VCL testtool"
| Line 1: | Line 1: | ||
| − | How to use QA testtool | + | ==== How to use QA 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. | 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) | 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 isolate OpenOffice.org environment and do not break ones setting for tests | ||
| Line 12: | 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? === | |
Release sanity test usually takes about 15hours regardless of the platform, e.g., CPU etc. | Release sanity test usually takes about 15hours regardless of the platform, e.g., CPU etc. | ||
| − | + | === Available documents === | |
Windows XP :http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7469 | Windows XP :http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7469 | ||
| Line 28: | Line 27: | ||
MacOSX PPC : http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7672 | MacOSX PPC : http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7672 | ||
MacOSX Intel : http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7553 | MacOSX Intel : http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7553 | ||
| + | |||
| + | [[Category:Quality Assurance]] | ||
Revision as of 06:26, 11 January 2007
Contents
How to use QA 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 QAtest take?
Release sanity test usually takes about 15hours regardless of the platform, e.g., CPU etc.
Available documents
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 :
Solaris 10 (i386) : http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7491 Solaris 10 (1386) : http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7490 Fedora Core 6 : http://wiki.services.openoffice.org/wiki/Testtool_FD6_en Fedora Core 6 : http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7495 MacOSX PPC : http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7672 MacOSX Intel : http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7553
