If you run automated tests with VCL Testtool, then please read this message.
Testautomation will remove the file testautomation/global/hid/hid.lst.
But the file hid.lst is essential for running automated tests with VCL
TestTool.
The File matches the number of an UI element known by OOo to a speaking
name, used in VCL TestTool test scripts.
Where do I get the file, now?
-----------------------------
The file is generated on building OOo.
There are several ways to get it:
- It will be put into the testautomation archives provided by Maho Nakata:
http://ooopackages.good-day.net/pub/OpenOffice.org/qa/testautomation/
If you use these test environment archives, there is no action for
you.
- If the package 'TestTool' got selected during installation of OOo,
the file hid.lst is found in basis-program directory.
TestTool recognizes this and copies it to the default location
(testautomation/global/hid/).
If there is no writeaccess to the directory, a message is thrown and
VCL TestTool aborts. Then the hid-directory location needs to get
changed in the VCL TestTool settings, where writeaccess is allowed.
- The file will be put on Quaste:
http://quaste.services.openoffice.org/index.php?option=com_quaste&task=tests_overview&workspace=DEV300&milestone=m53&download=2
The version 'DEV300' and 'm53' needs to get adjusted to your needs.
Download it and save it to your hid-directory location as set in
VCL TestTool, and name it 'hid.lst'.
VCL TestTool tries to find the file automatical, if it does not succeed
a message is thrown and it ends.
Action required?
----------------
The version of hid.lst should match the version of OOo.
The version is written on the first line of hid.lst, and
is printed out on startup of VCL TestTool.
If the versions do not match, a mesage is printed, and the test goes on.
There might be problems if the version differs a few,
but need not.
There are problems, if the versions differ too much.
What changes on compiling OOo?
------------------------------
A new switch is introduced to 'configure': --enable-hids
This is needed to build a new hid.lst.
If it is omitted, the old behaviour takes place, which uses a static
hid.lst from module helpcontent2 - which is far too old.
Buildbot behaviour will change soon, too.
They will use the switch, so a current hid.lst file is put into
installation sets.
When will the change be activated?
----------------------------------
Now, with the upcoming build of OOo DEV300 m53
Known Problems:
---------------
There are currenty about 99 warnings in the beginning, which are already
fixed in CWS dba32e: i103219, but is not yet integrated into the master.
It disturbs only a few database tests.
cheers
Thorsten [email protected]
--
*******************************************************************
Thorsten Bosbach Sun Microsystems GmbH
Quality Assurance Engineer 20097 Hamburg, Germany
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
