content/porting/freebsd/qa/index.html - openoffice-org - Git at Google

 <html>
 <head>
 <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
 <title>FreeBSD OpenOffice.org porting status page : Quality Assurance and known issues</title>
 </head>
 <body>
 <h2>FreeBSD OpenOffice.org porting status page : Quality Assurance</h2>

 <p>$Id: QA.html,v 1.21 2005/12/01 07:19:41 maho Exp $</p>
 by <a href="mailto:openoffice@FreeBSD.org">OpenOffice.org porting team</a>
 and <a href="mailto:maho@FreeBSD.org">NAKATA, Maho</a>

 <h3>Quality Assurance</h3>
 Once porting has been done, it means that the OOo source is buildable. The next step should be to perform Quality Assurance of the FreeBSD ported OpenOffice.org. This consists of several parts. Automated QA testing is also available. Other testcases are always needed.

 <h3>Automated QA</h3>
 Basic functionality of OpenOffice.org can be tested via automated GUI tools. The testtool connects OOo via TCP/IP, and does partial testing. Before proceeding, you should read
 <a href="http://www.openoffice.org/qa/qatesttool/">Automated GUI Testing</a>,
 <a href="http://www.openoffice.org/qa/qatesttool/OOo_testtool.pdf">Introduction to Automated GUI Testing</a>, and <a href="http://www.openoffice.org/qa/qatesttool/OOo_tt_CookBook.pdf">OpenOffice.org TestTool CookBook</a>.

 <br>
 <h4>Testing OpenOffice.org 2.0</h4>
 <ul>
 <li> Install OpenOffice.org 2.0 via port:
 <pre>
 # cd /usr/ports/editors/openoffice.org-2.0
 # make install
 </pre>
 <li> Prepare some directory (this affects .testtoolrc)
 <pre>
 % mkdir /work/ooo/2.0
 </pre>
 <li> Checkout QA test scripts
 <pre>
 % cd /work/ooo/2.0
 % cvs -d:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs co qa/qatesttool
 </pre>
 CAUTION: you must checkout appropreate qa/qatesttool otherwise meaningless. Please refer <a href="http://blogs.sun.com/roller/page/liegerad?catname=%2FSun">qa/qatesttool cvs tags and branches</a>. If you want to test OOo 2.0.0, check out
 by:
 <pre>
 % cd /work/ooo/2.0
 % cvs -d:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs co -r OOO200final qa/qatesttool
 </pre>
 2.0.1 (currently in the works until it will out)
 <pre>
 % cd /work/ooo/2.0
 % cvs -d:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs co -r OOO201 qa/qatesttool
 </pre>

 <li> Write .testtoolrc<br>
 Just copying and pasting this section into ~/.testtollrc is enough.
 You can change some directories/profile/hardcoded names, etc., if you'd like. <br>
 The following part is the most important:
 <pre>
 [OooProgramDir]
 Current=/usr/local/openoffice.org2.0/
 All=/usr/local/openoffice.org2.0/
 </pre>
 You must change to another directory if you installed the newer port
 (RC2 or 2.0 or 2.0.1 or developer version). you can check by typing:
 <pre>
 %cd /usr/ports/editors/openoffice.org-2.0-devel
 % make -V INSTALLATION_BASEDIR
 openoffice.org2.0m140
 </pre>
 for example
 and you can download from here <a href="testtoolrc2">testtoolrc2</a>.
 please rename to .testtoolrc and change appropreately before using it.

 <li> Install bash via ports
 <pre>
 % su
 Password:
 # cd /usr/ports/shells/bash
 # make install clean
 </pre>

 <li> Apply following patch to qa/qatesttool/script/unix/OOoTestRun_unix.sh
 (just setting sLocation, LD_LIBRARY_PATH and sTestTool appropriately)
 <pre>
 --- qa/qatesttool/script/unix/OOoTestRun_unix.sh        Thu Sep  8 17:51:36 2005
 +++ qa/qatesttool/script/unix/OOoTestRun_unix.sh  Thu Oct 13 11:30:26 2005
 @@ -43,11 +43,12 @@

  # set location of testscripts
  # (the directory, where directory 'qatesttool' exists)
 -sLocation=/testtool
 +sLocation=/work/ooo/2.0/qa/

  # set location of TestTool
  # (full path including executable 'testtool')
 -sTestTool=/testtool/linux/testtool
 +sTestTool=/usr/local/openoffice.org2.0.RC1/program/testtool.bin
 +LD_LIBRARY_PATH=/usr/local/openoffice.org2.0.RC1/program; export LD_LIBRARY_PATH

  # set location of close-office file
  # (see cvs)

 </pre>
 <li> Run OOoTestRun_unix.sh
 <pre>
 % cd /work/ooo/2.0/
 % bash qa/qatesttool/script/unix/OOoTestRun_unix.sh
 </pre>

 <li> running VCL testtool in background
 <blockquote>
 if you are running testtool, you cannot do anything other than QA. you cannot run OOo, you need X terminal dedicated to QA, etc. to QA in background, I wrote a shell script. this does clean test, removing user settings and logs everytime.
 <a href="oooqa20.sh">oooqa20.sh</a>. You should create a new user like oooqa20, then
 <pre>
 login: oooqa20
 ...
 % bash oooqa20.sh
 </pre>
 Of course, I assume you are QA expert :)
 </blockquote>
 <li> Diagnostics: Logs are accumulated in qa/qatesttool/errorlog/maho/*res
 </ul>
 <hr>

 <h4> Testing OpenOffice.org 1.1.5 </h4>
 You need the GNU/Linux version of qatesttool to run. Currently, my FreeBSD build of
 the testtool are broken and I don't know how to fix it...
 <ul>
 <li> Activate linux ABI via ports
 <pre>
 # cd /usr/ports/emulators/linux_base-rh-9/
 # make install
 </pre>
 <li> Install OpenOffice.org 1.1.5 via port: (do not delete the work directory!!)
 and copy the necessary library named libsts645fi.so to /usr/local/OpenOffice.org1.1.5/program/.
 <pre>
 # cd /usr/ports/editors/openoffice.org-1.1
 # make install
 # cp /usr/ports/editors/openoffice.org-1.1/work/OOo_1.1.5/solver/645/unxfbsd.pro/lib/libsts645fi.so /usr/local/OpenOffice.org1.1.5/program/
 </pre>

 <li> Make sure OpenOffice.org 1.1.5 user installation has been completed
 <pre>
 % openoffice.org-1.1.5
 ...
 </pre>
 Do you have ~/.sversionrc and ~/OpenOffice.org1.1.5?
 <pre>
 % ls ~/.sversionrc
 /home/maho/.sversionrc
 % ls ~/OpenOffice.org1.1.5/
 LICENSE                         setup@
 LICENSE.html                    setup.log
 README                          share/
 README.html                     soffice@
 THIRDPARTYLICENSEREADME.html    spadmin@
 instdb.ins                      user/
 program/
 </pre>
 If so, then you're okay.

 <li>Prepare the qa directory
 <pre>
 % mkdir /work/ooo/1.1.5
 </pre>

 <li> Download the testtool (linux version)
 <pre>
 % cd /work/ooo/
 % fetch http://www.openoffice.org/qa/qatesttool/11beta/tt_645m5_linux.tar.gz
 % tar xvfz tt_645m5_linux.tar.gz
 </pre>

 <li> Checkout QA test scripts for 1.1.5 (tag is ooo115)
 <pre>
 % cd /work/ooo/1.1.5
 % cvs -d:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs co -r ooo115 qa/qatesttool
 </pre>
 for 1.1.4 and 1.1.3 please use branch (tag) ooo114, ooo113, respectively.
 <li> Write ~/.testtoolrc (do not mix with 2.0s one)
  you can also download from here <a href="testtoolrc1">testtoolrc1</a>.<br>
 please rename to .testtoolrc and change appropreately before using it.

 <li> Apply <a href="qa_ooo115_fbsd.diff">qa_ooo115_fbsd.diff</a> this patch to qa/qatesttool

 <li> Run OOoTestRun_unix.sh
 <pre>
 % cd /work/ooo/1.1.5
 % bash qa/qatesttool/script/unix/OOoTestRun_unix.sh
 </pre>

 <li> running VCL testtool in background
 <blockquote>
 if you are running testtool, you cannot do anything other than QA. you cannot run OOo, you need X terminal dedicated to QA, etc. to QA in background, I wrote a shell script. this does clean test, removing user settings and logs everytime.
 <a href="oooqa11.sh">oooqa11.sh</a>. You should create a new user like oooqa11, then
 <pre>
 login: oooqa11
 ...
 % bash oooqa11.sh
 </pre>
 Of course, I assume you are QA expert :)
 </blockquote>

 <li> Diagnostics:
 Logs are accumulated at qa/qatesttool/errorlog/maho/*res
 </ul>

 <hr>
 <ul>
 Some pitfalls
 <li> [OooProgramDir]
 <blockquote>
 If you install different version of OOo, you must change this.
 </blockquote>
 <li> [Communication]
 <blockquote>
 if you want to run QA 1.1.5 and 2.0 at the same time, you must change the port number, and port numbers
 are arbitrary, but never be the same.
 </blockquote>
 </ul>
 <br>
 <hr>
 Links
 <ul>
 <li> <a href="http://www.openoffice.org/qa/">Quality assurance project</a>
 <li> <a href="http://www.openoffice.org/qa/localized/index.html">QA for localized builds</a>
 <li> <a href="http://www.openoffice.org/qa/localized/status.html">OpenOffice.org 1.1.4 Localization Status</a>
 <li> <a href="http://blogs.sun.com/roller/page/liegerad?catname=%2FSun">qa/qatesttool cvs tags and branches</a>
 </ul>
 <hr>
 </body>
 </html>
	<html>
	<head>
	<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
	<title>FreeBSD OpenOffice.org porting status page : Quality Assurance and known issues</title>
	</head>
	<body>
	<h2>FreeBSD OpenOffice.org porting status page : Quality Assurance</h2>

	<p>$Id: QA.html,v 1.21 2005/12/01 07:19:41 maho Exp $</p>
	by <a href="mailto:openoffice@FreeBSD.org">OpenOffice.org porting team</a>
	and <a href="mailto:maho@FreeBSD.org">NAKATA, Maho</a>

	<h3>Quality Assurance</h3>
	Once porting has been done, it means that the OOo source is buildable. The next step should be to perform Quality Assurance of the FreeBSD ported OpenOffice.org. This consists of several parts. Automated QA testing is also available. Other testcases are always needed.

	<h3>Automated QA</h3>
	Basic functionality of OpenOffice.org can be tested via automated GUI tools. The testtool connects OOo via TCP/IP, and does partial testing. Before proceeding, you should read
	<a href="http://www.openoffice.org/qa/qatesttool/">Automated GUI Testing</a>,
	<a href="http://www.openoffice.org/qa/qatesttool/OOo_testtool.pdf">Introduction to Automated GUI Testing</a>, and <a href="http://www.openoffice.org/qa/qatesttool/OOo_tt_CookBook.pdf">OpenOffice.org TestTool CookBook</a>.

	<br>
	<h4>Testing OpenOffice.org 2.0</h4>
	<ul>
	<li> Install OpenOffice.org 2.0 via port:
	<pre>
	# cd /usr/ports/editors/openoffice.org-2.0
	# make install
	</pre>
	<li> Prepare some directory (this affects .testtoolrc)
	<pre>
	% mkdir /work/ooo/2.0
	</pre>
	<li> Checkout QA test scripts
	<pre>
	% cd /work/ooo/2.0
	% cvs -d:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs co qa/qatesttool
	</pre>
	CAUTION: you must checkout appropreate qa/qatesttool otherwise meaningless. Please refer <a href="http://blogs.sun.com/roller/page/liegerad?catname=%2FSun">qa/qatesttool cvs tags and branches</a>. If you want to test OOo 2.0.0, check out
	by:
	<pre>
	% cd /work/ooo/2.0
	% cvs -d:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs co -r OOO200final qa/qatesttool
	</pre>
	2.0.1 (currently in the works until it will out)
	<pre>
	% cd /work/ooo/2.0
	% cvs -d:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs co -r OOO201 qa/qatesttool
	</pre>

	<li> Write .testtoolrc<br>
	Just copying and pasting this section into ~/.testtollrc is enough.
	You can change some directories/profile/hardcoded names, etc., if you'd like. <br>
	The following part is the most important:
	<pre>
	[OooProgramDir]
	Current=/usr/local/openoffice.org2.0/
	All=/usr/local/openoffice.org2.0/
	</pre>
	You must change to another directory if you installed the newer port
	(RC2 or 2.0 or 2.0.1 or developer version). you can check by typing:
	<pre>
	%cd /usr/ports/editors/openoffice.org-2.0-devel
	% make -V INSTALLATION_BASEDIR
	openoffice.org2.0m140
	</pre>
	for example
	and you can download from here <a href="testtoolrc2">testtoolrc2</a>.
	please rename to .testtoolrc and change appropreately before using it.

	<li> Install bash via ports
	<pre>
	% su
	Password:
	# cd /usr/ports/shells/bash
	# make install clean
	</pre>

	<li> Apply following patch to qa/qatesttool/script/unix/OOoTestRun_unix.sh
	(just setting sLocation, LD_LIBRARY_PATH and sTestTool appropriately)
	<pre>
	--- qa/qatesttool/script/unix/OOoTestRun_unix.sh Thu Sep 8 17:51:36 2005
	+++ qa/qatesttool/script/unix/OOoTestRun_unix.sh Thu Oct 13 11:30:26 2005
	@@ -43,11 +43,12 @@

	# set location of testscripts
	# (the directory, where directory 'qatesttool' exists)
	-sLocation=/testtool
	+sLocation=/work/ooo/2.0/qa/

	# set location of TestTool
	# (full path including executable 'testtool')
	-sTestTool=/testtool/linux/testtool
	+sTestTool=/usr/local/openoffice.org2.0.RC1/program/testtool.bin
	+LD_LIBRARY_PATH=/usr/local/openoffice.org2.0.RC1/program; export LD_LIBRARY_PATH

	# set location of close-office file
	# (see cvs)

	</pre>
	<li> Run OOoTestRun_unix.sh
	<pre>
	% cd /work/ooo/2.0/
	% bash qa/qatesttool/script/unix/OOoTestRun_unix.sh
	</pre>

	<li> running VCL testtool in background
	<blockquote>
	if you are running testtool, you cannot do anything other than QA. you cannot run OOo, you need X terminal dedicated to QA, etc. to QA in background, I wrote a shell script. this does clean test, removing user settings and logs everytime.
	<a href="oooqa20.sh">oooqa20.sh</a>. You should create a new user like oooqa20, then
	<pre>
	login: oooqa20
	...
	% bash oooqa20.sh
	</pre>
	Of course, I assume you are QA expert :)
	</blockquote>
	<li> Diagnostics: Logs are accumulated in qa/qatesttool/errorlog/maho/*res
	</ul>
	<hr>

	<h4> Testing OpenOffice.org 1.1.5 </h4>
	You need the GNU/Linux version of qatesttool to run. Currently, my FreeBSD build of
	the testtool are broken and I don't know how to fix it...
	<ul>
	<li> Activate linux ABI via ports
	<pre>
	# cd /usr/ports/emulators/linux_base-rh-9/
	# make install
	</pre>
	<li> Install OpenOffice.org 1.1.5 via port: (do not delete the work directory!!)
	and copy the necessary library named libsts645fi.so to /usr/local/OpenOffice.org1.1.5/program/.
	<pre>
	# cd /usr/ports/editors/openoffice.org-1.1
	# make install
	# cp /usr/ports/editors/openoffice.org-1.1/work/OOo_1.1.5/solver/645/unxfbsd.pro/lib/libsts645fi.so /usr/local/OpenOffice.org1.1.5/program/
	</pre>

	<li> Make sure OpenOffice.org 1.1.5 user installation has been completed
	<pre>
	% openoffice.org-1.1.5
	...
	</pre>
	Do you have ~/.sversionrc and ~/OpenOffice.org1.1.5?
	<pre>
	% ls ~/.sversionrc
	/home/maho/.sversionrc
	% ls ~/OpenOffice.org1.1.5/
	LICENSE setup@
	LICENSE.html setup.log
	README share/
	README.html soffice@
	THIRDPARTYLICENSEREADME.html spadmin@
	instdb.ins user/
	program/
	</pre>
	If so, then you're okay.

	<li>Prepare the qa directory
	<pre>
	% mkdir /work/ooo/1.1.5
	</pre>

	<li> Download the testtool (linux version)
	<pre>
	% cd /work/ooo/
	% fetch http://www.openoffice.org/qa/qatesttool/11beta/tt_645m5_linux.tar.gz
	% tar xvfz tt_645m5_linux.tar.gz
	</pre>

	<li> Checkout QA test scripts for 1.1.5 (tag is ooo115)
	<pre>
	% cd /work/ooo/1.1.5
	% cvs -d:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs co -r ooo115 qa/qatesttool
	</pre>
	for 1.1.4 and 1.1.3 please use branch (tag) ooo114, ooo113, respectively.
	<li> Write ~/.testtoolrc (do not mix with 2.0s one)
	you can also download from here <a href="testtoolrc1">testtoolrc1</a>.<br>
	please rename to .testtoolrc and change appropreately before using it.

	<li> Apply <a href="qa_ooo115_fbsd.diff">qa_ooo115_fbsd.diff</a> this patch to qa/qatesttool

	<li> Run OOoTestRun_unix.sh
	<pre>
	% cd /work/ooo/1.1.5
	% bash qa/qatesttool/script/unix/OOoTestRun_unix.sh
	</pre>

	<li> running VCL testtool in background
	<blockquote>
	if you are running testtool, you cannot do anything other than QA. you cannot run OOo, you need X terminal dedicated to QA, etc. to QA in background, I wrote a shell script. this does clean test, removing user settings and logs everytime.
	<a href="oooqa11.sh">oooqa11.sh</a>. You should create a new user like oooqa11, then
	<pre>
	login: oooqa11
	...
	% bash oooqa11.sh
	</pre>
	Of course, I assume you are QA expert :)
	</blockquote>

	<li> Diagnostics:
	Logs are accumulated at qa/qatesttool/errorlog/maho/*res
	</ul>

	<hr>
	<ul>
	Some pitfalls
	<li> [OooProgramDir]
	<blockquote>
	If you install different version of OOo, you must change this.
	</blockquote>
	<li> [Communication]
	<blockquote>
	if you want to run QA 1.1.5 and 2.0 at the same time, you must change the port number, and port numbers
	are arbitrary, but never be the same.
	</blockquote>
	</ul>
	<br>
	<hr>
	Links
	<ul>
	<li> <a href="http://www.openoffice.org/qa/">Quality assurance project</a>
	<li> <a href="http://www.openoffice.org/qa/localized/index.html">QA for localized builds</a>
	<li> <a href="http://www.openoffice.org/qa/localized/status.html">OpenOffice.org 1.1.4 Localization Status</a>
	<li> <a href="http://blogs.sun.com/roller/page/liegerad?catname=%2FSun">qa/qatesttool cvs tags and branches</a>
	</ul>
	<hr>
	</body>
	</html>