VCL TestTool/Standalone VCL TestTool

The standalone version is a package with just the VCL TestTool binaries. All needed libraries are extracted from a complete OOo binary version and so it is just about 60MB in size. This is done, to keep this TestTool on your computer and use it for testing OOo. We strongly not recommend on using the TestTool version from the OOo package that comes with every build. We want to test OOo and not the TestTool - and thus you have to keep some things constant to be sure the found errors are in the OOo application and not in the TestTool! It sometimes happen, that changes to OOo break the TestTool - some are obvious, some not.

How to build your own stand alone TestTool

This is broken since SRC680m242
As a workaround you have to use the testtool.bin in the program directory of an installed OOo.
For MacOS X please look at the end of this page

• Some excuse: it is an old perl script ;-)
• You find it in cvs:

qa/qatesttool/tools/standaloneTestTool

• You need a file with the needed files for your platform file*.txt

There already exist some that you may use as template:

filelinx.txt, fileosx.txt, filesoli.txt, filesols.txt, filewin.txt

• You further need either an OOo installation or the build directories;
• You start the creation by calling the script createTestTool.pl with some parameters:

 createTestTool.pl file...txt /office_installation/ /createhere/

• The script is a little dumb, so please respect the following:
  • All paths have to end with the path seperator
  • If you create from an office installation, don't include the program directory, use the path with out program directory

not home/OOo2.3/program/, -> use home/OOo2.3/

• • If you use an build environment, use the lib path: /SRX644/unxlngi4.pro/lib.m226/
• At the end the missing libraries are reported;
• If you used an OOo installation you miss the icon package; download here and extrakt into your testtool directory images_tt.zip
• You end up with the directory and a tar file; The tar file is just for easy extracting in another place, since it keeps the symlinks.

MacOS X

For MacOS X you may create an Application like the OOo Application package. (I'm currently enhancing the script to create an package for Mac OS X) A quick way would be:

• Make a copy of the OOo.app to TestTool.app
• In the file TestTool.app/Contents/Info.plist change 'soffice.bin' to 'testtool.bin'

• Root - CFBundleExecuteable

• It is recommended to use the 'Property List Editor', but I think you need the XCode developer package for this.

• Then it is just a click on Info.plist to start the editor.

• Delete all fileextension associations in Info.plist before starting, and maybe set the extensions inc, bas, win, sid, lst!

• Root - CFBundleDocumentTypes

• Set the creator code to OOT2; Complete list at end of issue 60840

• Root - CFBundleSignature

• Start by clicking TestTool in Finder