blob: 981172148596b0d3086e386354eaae665efe561c [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<head>
<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8">
<TITLE></TITLE>
<META NAME="GENERATOR" CONTENT="OpenOffice.org 2.0 (Unix)">
<META NAME="CREATED" CONTENT="20060903;21244500">
<META NAME="CHANGED" CONTENT="20060903;21445200">
</head>
<body LANG="de-DE" DIR="LTR">
<P>OpenOffice.org Conference (OOoCon 2006)<BR>QA &amp;
Testing<BR>Wednesday September 13th 2006 10:15 - 11:00</P>
<P>Getting started with automated GUI testing - the VCL TestTool
application<BR>The VCL TestTool Application is used to test the
functionality which is available via the graphical user interface of
OpenOffice.org.<BR>Step by step hands on session:</P>
<UL>
<LI><P>Where is the VCL TestTool Application?</P>
<LI><P>Where are the test scripts?</P>
<LI><P>What steps are needed on using the VCL TestTool Application
for the first time?</P>
</UL>
<P>The test scripts make sure that the general functions of OOo are
available and working. Automated testing makes it easy to check if
OOo behaves equaly on different platforms and languages with a
minimum manual effort.</P>
<P>Be prepared with:</P>
<OL>
<LI><P><B>An installed OpenOffice.org office suite</B></P>
<LI><P><B>The VCL TestTool application</B><BR>It is in the 'program'
directory of the OOo installation. The same directory where the
executable 'soffice' is found. On platforms others than win32 it is
necessary to copy the script 'soffice' to 'testtool' to get some
library paths set. The TestTool application is then started by
executing 'testtool'. (Which will start the binary 'testtool.bin').
If there are problems with the newest TestTool application 2.0.4,
use the TestTool from the last milestone 2.0.3.</P>
<LI><P><B>The TestTool Environment (scripts and documentation)</B><BR>It
is available from OOo CVS system. You will need a version of the
program 'cvs' and execute on the command line:<BR><I>cvs -d
:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs
login</I><BR>(password: none - just press return) <BR><I>cvs -d
:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs co -P
qa/qatesttool</I><BR>Since the scripts get nearly daily updates, it
doesn't make sense to provide downloadable archives. For this
presentation I put an archive together
of<BR>qa/qatesttool/errrorlog<BR>qa/qatesttool/global<BR>qa/qatesttool/framework/first<BR><A HREF="http://qa.openoffice.org/qatesttool/OOoCon2006/qa_cvs_global.zip">http://qa.openoffice.org/qatesttool/OOoCon2006/qa_cvs_global.zip</A>
(6MB)</P>
</OL>
<P>Cheers<BR>Thorsten Bosbach</P>
<P>--
<BR>*******************************************************************<BR>Thorsten
Bosbach, Sun Microsystems GmbH<BR>Quality
Assurance Engineer, 20097 Hamburg, Germany
</P>
</body>
</HTML>