Issue 111558 - allow override of tested soffice process
Summary: allow override of tested soffice process
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: DEV300m77
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 3.3
Assignee: Stephan Bergmann
QA Contact: issues@tools
Depends on:
Reported: 2010-05-12 16:31 UTC by Stephan Bergmann
Modified: 2010-06-18 08:53 UTC (History)
2 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---

implementation (12.16 KB, text/plain)
2010-05-12 16:33 UTC, Stephan Bergmann
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Stephan Bergmann 2010-05-12 16:31:20 UTC
For various reasons, it would be useful if the tests based on
solenv/inc/ (smoketestoo_native, */qa/unoapi, etc.) would not
always use the soffice program from the solver OOo installation (placed there by
smoketestoo_native), but if the user could manually override that.
Comment 1 Stephan Bergmann 2010-05-12 16:33:02 UTC
Created attachment 69436 [details]
Comment 2 Stephan Bergmann 2010-05-12 16:34:48 UTC
The attached DEV300_m77-ooo_test_soffice.patch would solve this, and reportedly
works as desired on Linux (sb) and Windows (iha).
Comment 3 Stephan Bergmann 2010-05-14 08:50:07 UTC
adapted DEV300_m77-ooo_test_soffice.patch applied as
Comment 4 Stephan Bergmann 2010-05-14 08:51:44 UTC
verified on unxsoli4; both smoketestoo_native (C++ based) and
configmgr/qa/unoapi (Java based) work with OOO_TEST_SOFFICE=path:... and
Comment 5 Stephan Bergmann 2010-05-14 08:56:32 UTC

The OOO_TEST_SOFFICE environment variable can be used to override which soffice
executable is used by the tests based on solenv/inc/
(smoketestoo_native, */qa/unoapi, ...).

When set as

  OOO_TEST_SOFFICE=path:<full pathname of soffice executable>

the tests do not use the soffice executable from the solver installation
(installed there by smoketestoo_native), but instead the specified one.  The
argument must be the complete, platform native pathname of the soffice
executable (i.e., on Unix it must end in ".../soffice" and on Windows in
".../soffice.exe"; on Windows it must not be a Cygwin-style "/cygdrive/..."
path).  The tests still start that soffice executable with a temporary user
installation, and still terminate it when finished testing.

When set as

  OOO_TEST_SOFFICE=connect:<URP connection description>

the tests do not start an soffice executable at all, but instead try to connect
to one via the given URP connection.  The argument must be the connection string
without the trailing ";urp" (e.g., "socket,host=localhost,port=12345" or
"pipe,name=foo").  The tests still try to terminate the connected soffice
process when finished (via, but no longer
notice if the soffice process crashes during termination (i.e., the tests do not
wait on the soffice process).

(When OOO_TEST_SOFFICE is set while building smoketestoo_native, the OOo solver
installation is still created, even though it is not used for the current test.
 On Windows, when OOO_TEST_SOFFICE is set, no temporary OOo installation is
unpacked by any of the tests.)
Comment 6 Stephan Bergmann 2010-05-20 08:33:19 UTC
... additional quoting fix
Comment 7 Stephan Bergmann 2010-06-18 08:53:46 UTC