Date: prev next · Thread: first prev next last

Hi all,

Following Sophie's announcement about QA testing and the use of Litmus,
I thought I'd try and use the VCLTesttool.

On Mac, the user/tester has to know that testtool.bin is stored in the
app bundle under LibreOffice/Contents/basis-link/program/testtool.bin.
There is also a symbolic link to the same binary in

However, if I try to start the LO 3.3.3rc1 testtool from a terminal :

/Applications/ ; exit;
2011-06-06 11:07:04.563 testtool.bin[7596:903] No Info.plist file in
application bundle or no NSPrincipalClass in the Info.plist file, exiting
2011-06-06 11:07:04.566 testtool.bin[7596:903] ***
__NSAutoreleaseNoPool(): Object 0x3906270 of class
RemoteControlContainer autoreleased with no pool in place - just leaking
2011-06-06 11:07:04.566 testtool.bin[7596:903] ***
__NSAutoreleaseNoPool(): Object 0x3906230 of class
MultiClickRemoteBehavior autoreleased with no pool in place - just leaking

and of course, the app doesn't launch the testtool.

The way to get VCLTestTool to launch is to use the symbolic link via a
terminal in the LibreOffice/Contents/MacOS directory.

Now, where are the *.bas files for testing. Since I happen to have the
source repo, I can find a collection in


but are they provided anywhere else separately ?


Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.