Testtool MacOSX PPC
Contents
Platform
* MacOSX PPC Panther version or later * OOo 2.1RC2 Japanese version
for 3.0.0 or later OpenOffice.org became Mac OS X native.
For 2.x MacOSX Tiger with PPC, X11 is too unstable, still I cannot identify the problem but X11 terminates consistently in some tests I don't remember.
How to obtain OS
Come with Mac G5 ;)
Update the OS
- in English
System Preferences -> Software update
- in Japanese
システム環境設定 -> ソフトウェアアップデート
OS specific settings; disabling screen saver and some tips.
- in English
- System Preferences -> Desktop & screen saver -> Screen Saver -> Start screen saver -> never
- System Preferences -> Energy Saver -> Put the computer to sleep when it is inactive for -> never
- System Preferences -> Energy Saver -> Put the computer to sleep Put the display to sheep when the compute is in active for: -> never
in Japanese 日本語
- システム環境設定->デスクトップとスクリーンセーバー->スクリーンセーバーを開始->しない
- 省エネルギー->スリープ->コンピュータがスリープスルまでの待機時間->しない
- 省エネルギー->スリープ->ディスプレイがスリープスルまでのコンピュータの待機時間->しない
Download OOo and install them.
For 3.x
- OOo 3.x
download from ftp://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/ .
- QA scripts
download from ftp://ooopackages.good-day.net/pub/OpenOffice.org/qa/testautomation/ .
you can see the detail of release on [Product_Release/builds_uploaded|Build Update Page]
For 2.x
- OOo 2.1RC2
$ ftp ftp://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/2.1.0rc2_20061130/OOo_2.1.0rc2_20061130_MacOSXIntel_install_ja.dmg
- QA scripts
$ ftp ftp://ftp.ooodev.org/pub/qa/qatesttool_ooo201_20062311.tgz
- Verification of MD5SUMs
% md5 OOo_2.1.0rc2_20061130_MacOSXPPC_install_ja.dmg qatesttool_ooo201_20062311.tgz MD5 (OOo_2.1.0rc2_20061130_MacOSXPPC_install_ja.dmg) = c5915722f66a42742e37f41a2d79a566 MD5 (qatesttool_ooo201_20062311.tgz) = d43d1ed59ea7bd10330be1276d79c6b1
MD5sum of OOo packages: http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=10273 MD5 sum of qatesttool script: http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7328
installation
For 3.x
- double click downloaded package.
- drag and drop to Application folder
You do not need X11
For 2.x
double click OOo_2.1.0rc2_20061130_MacOSXIntel_install_ja.dmg -> drag and drop to Application folder
- installation of X11.
Disk 3 of OS installation media, you can install X11 from X11.pkg. See http://www.apple.com/jp/articles/tutorial/panther/vol2_3_2.html (in Japanese)
Preparation for QA
For 3.x
Use the QAscript folder/tools/run_tests/run_tests.sh
For 2.x
(For Japanese only: recognition of IPA font by spadmin X11 -> X terminal % /Applications/OpenOffice.org\ 2.1.app/Contents/MacOS/program/spadmin )
- preparation for testtool
% cp /Applications/OpenOffice.org\ 2.1.app/Contents/MacOS/program/soffice /Applications/OpenOffice.org\ 2.1.app/Contents/MacOS/program/testtool
sudo mkdir /work
$ sudo chown maho /work $ cd /work $ mkdir qa ; cd qa $ tar xvfz ~/qatesttool_ooo201_20062311.tgz $ cd qa/qatesttool/script/unix
- apply following patch to ooo_releasetest.sh
see also: http://www.openoffice.org/issues/show_bug.cgi?id=70761 --- ooo_releasetests.sh.org 2006-12-15 09:13:57.000000000 +0900 +++ ooo_releasetests.sh 2006-12-15 09:15:16.000000000 +0900 @@ -44,12 +44,12 @@ # set location of testscripts # (the directory, where directory 'qatesttool' exists) -sLocation=/testtool +sLocation=/work/qa # set location of TestTool # (full path including executable 'testtool') -sTestTool="/opt/openoffice.org2.0/program/testtool.bin" +sTestTool="/Applications/OpenOffice.org 2.1.app/Contents/MacOS/program/testtool" # set location of close-office file # (see cvs) @@ -101,9 +101,9 @@ do echo "Running soffices' processes: " # kill office, if exists - #killall -9 soffice.bin - pkill -9 soffice.bin - ps -fe | grep $USER | grep "soffice.bin" | grep -v "grep" + /usr/bin/killall -9 soffice.bin + #pkill -9 soffice.bin + ps -Aj | grep $USER | grep "soffice.bin" | grep -v "grep" echo "****************************************************" echo "Will run: " $x @@ -119,14 +119,14 @@ testtoolpid=$! echo "PID of Testtool: " $testtoolpid - if ps -p $testtoolpid > /dev/null ; then + if ps -p $testtoolpid | grep $testtoolpid > /dev/null ; then echo " Successfully started" else echo " There might be something wrong with starting the Testtool!" fi ######### wait until Testtool has finished & closed - while ps -p $testtoolpid > /dev/null ; + while ps -p $testtoolpid | grep $testtoolpid > /dev/null ; do sleep 2 i=$((i+2))
Prepare ~/Library/Application\ Support/.testtoolrc
[Misc] CurrentProfile=_profile_Default ServerTimeout=4500 [Crashreporter] UseProxy=false ProxyServer=none ProxyPort=8080 AllowContact=false ReturnAddress= [_profile_Default] BaseDir=/work/qa/qatesttool LogBaseDir=/work/qa/qatesttool/errorlog/ StopOnSyntaxError=0 HIDDir=/work/qa/qatesttool/global/hid *.bas=/work/qa/qatesttool/framework/first [GUI Platform] Current=12 [WinGeom] WinParams=0,44,920,630;1;0,0,0,0; [OooProgramDir] Current=/Applications/OpenOffice.org 2.1.app/Contents/MacOS/program All=/Applications/OpenOffice.org 2.1.app/Contents/MacOS/program [Communication] Host=localhost TTPort=12479 UNOPort=13480
Perform QA test
For 3.x
For 2.x
Application->X11->Xterm $ cd /work/qa/qatesttool/script/unix $ rm -rf ~/Library/Application\ Support/OpenOffice.org\ 2.1 /work/qa/qatesttool/errorlog/*res; bash ooo_releasetests.sh
Summary of the result
For 3.x
upload to Quaste
Summary:
For 2.x
in Issue http://www.openoffice.org/issues/show_bug.cgi?id=71978 Attached as http://www.openoffice.org/nonav/issues/showattachment.cgi/41530/errorlog-MacOSXPPC-OOo21jaQA.tar.gz
Summary: errors warnings warning during initialization ------------------------------------------------ b_updt.res 5 17 0 c_updt.res 1 0 0 ch_updt.res 0 0 0 d_updt.res 0 1 0 f_updt_help.res 0 0 0 f_updt_pkgmgr.res 1 1 0 f_updt_spadmin.res 0 0 0 f_updt_templates.res 0 4 0 f_updt_windowfuncs.res 0 0 0 first.res 0 1 0 gallery.res 1 3 0 i_updt_1.res 0 0 0 i_updt_2.res 0 1 0 m_updt.res 1 1 0 ma_updt.res 0 0 0 oasis_graphics_update.res 0 0 0 topten.res 0 0 0 w_updt.res 0 0 0 ww_updt.res 0 0 0 xforms_updt.res 0 0 0 ------------------------------------------------
Duration: 703 min 44 sec **************************************************** ************ FINISHED ************ **************************************************** 42911.62 real 626.13 user 767.68 sys (626.13+767.68)/42911.62 * 100 3.24809457205297772400 only 3% use of computer out of 703 min 44 sec. * 703min is quite short time period. Some tests are bypassed?
Orginal document:NAKATA, Maho (maho@FreeBSD.org)