VCLTesttool
Contents
About the TestTool
The TestTool is a standalone program that is used for the automated testing of OpenOffice.org. The TestTool communicates with the TCP/IP-Interface of OpenOffice.org and can test each installation of OpenOffice.org on a PC or in a local area network (LAN). The current TestTool can be used on OpenOffice.org 1.1beta and higher. However, as there can be some incompatible changes in future OpenOffice.org builds you may need to use a newer version of the TestTool. Current versions of TestTool can always be found here
Quick start
If you want to help in automated testing and start immediately this guide is the right choice for you. It offers a step-by-step guide to start with and is valid for testing OpenOffice.org-Version 3.x. However this guide claims to reach testers with basic and experienced knowledge too.
Prerequisite
If all prerequisites are met one can start with automated testing
CVS installed
One must have a working CVS on the system. Read CVS client setup to setup client to be used on OpenOffice.org
OpenOffice.org installed
One must have an installed office on the system and it is important to know what version has to be tested.
If you are not sure what version is installed on your system you can check version.ini (.versionrc on UNIX-Systems) in installation directory
(look in <INSTALLDIR>/OpenOffice.org 3/program)
Open file and see area [Version]:
Example:
ProductMajor=300
ProductMinor=29
ProductSource=DEV300
VCLTestTool
To be able start auomated testing of OpenOffice.org you must have a local copy of VCLTesttool on your system too.
Download current TestTool to a location of your choice on your local machine and extract the archive to your local system.
TestTool framework
The TestTool framework holds all scripts provided to test a milestone based on current branch. You can find all those files in OpenOffice.org CVS and can easily download them to your local file system via cvs checkout. Let's say you're about to test a version based on branch 'DEV300' with milestone 'm29'.
Use the following cvs command to get the sources: cvs checkout -r DEV300_m29 -d testautomation_m29 testautomation
(optional parameter -d is used to checkout into specific directory to be able holding more versions in parallel)
If all prerequisites are met one can start with automated testing
