Montag März 02, 2009 To be able to open a CWS for testautomation, you do not need to checkout everything from svn repository.
(As an example I used Mac OS X 10.4 PPC)
Create a new directory and go on with:
mkdir DEV300_m38
cd $_
svn checkout svn+ssh://svn@svn.services.openoffice.org/ooo/tags/DEV300_m38/config_office
svn checkout svn+ssh://svn@svn.services.openoffice.org/ooo/tags/DEV300_m38/solenv
svn checkout svn+ssh://svn@svn.services.openoffice.org/ooo/tags/DEV300_m38/dmake
svn checkout svn+ssh://svn@svn.services.openoffice.org/ooo/tags/DEV300_m38/moz
Now go into directory config_office and type ./configure with some switches from:
http://wiki.services.openoffice.org/wiki/AquaBuild#One-Time_preparations_and_scripts
When finished without errors, go up one level and type:
./bootstrap
After that do:
source MacOSXPPCEnv.Set.sh
There should now be the cws command available:
cws help
(Maybe you need to tweak your config a little: http://wiki.services.openoffice.org/wiki/CWS#cws_config_file_.28.cwsrc.29 )
cws create DEV300 tbo04
creates the CWS in the EIS database, but does not change something on your harddisk.
You are now able to start getting your needed testautomation files:
mkdir testautomation
cd $_
svn checkout svn+ssh://svn@svn.services.openoffice.org/ooo/cws/tbo04/testautomation/global
svn checkout svn+ssh://svn@svn.services.openoffice.org/ooo/cws/tbo04/testautomation/YOUR_WANTED_MODULE
Now you are able to begin your work by changing the files to testautomation.
Samstag August 09, 2008
The last major issue to be solved is the behaviour of the VCL TestTool application after OpenOffice.org crashed.
The quickstarter behaviour needs to get disabled for automated testing, which currently can not be triggered after a crash on MacOS X.
The winning issue which solves this is 86540 which will get integrated with cws gh15. Thanks to GH for getting this done.
In the meantime I also found a workaround for this: Registering a Basic macro to be executed on startup of OpenOffice.org.
Donnerstag Mai 15, 2008
The former problem is identified and solved; It was all about a focus problem:
The UI of OpenOffice.org is not completely updated when the application is not front most.
When VCL TestTool starts OpenOffice.org, the application is started behind
the VCL TestTool application. This prevents some UI updates on OpenOffice.org,
which would be necessary for some tests.
First solution, as a workaround, is calling OpenOffice.org.app with the shell command,
after the VCL TestTool started soffice.bin. This makes OOo the front most application.
The real solution is made by PL, binding some 'bring application to front' action
to the commandline switch '-enableautomation', which belongs to CWS aquavcl07.
So from now on, errors shown by automated testing on MacOS X, are real errors found in OpenOffice.org.
Dienstag März 25, 2008
The results of the ~40 category 0 tests are not quite satisfying.
Compared to other platforms the errors and warnings are huge.
The reason is currently not the quality of OpenOffice.org on MacOS, it is more an issue on how OpenOffice.org behaves on VCL TestTool.
Link to all issues.
Mittwoch Jänner 17, 2007
I want to give you an short update of the state for the new VCL TestTool Application for OOo 2.3.
The change will take place with CWS gh13 after releasing the next milestone of OOo: 2.2
It will be used to test OOo 2.3 and it's developer releases.
Montag November 28, 2005 Every release of OOo throws up the question:
Which cvs tag should I use to test OOo with the TestTool application?
Short answer for OOo 2.2. currently: take the HEAD - until ooo220 exists.
Longer answer...
[Read More] Gesendet von tbo ( Nov 28 2005, 04:28:07 PM CET ) PermalinkPage Hits heute: 14