Re: info/DEV300 CWS sb118 : OOo installation for smoketest/subsequenttests

Stephan Bergmann <[email protected]> Tue, 23 Mar 2010 15:02:10 +0100
Newsgroups gmane.comp.openoffice.announce.interface
Message-ID <[email protected]>
On 03/22/10 14:56, [email protected] wrote:
> 
>           Type: info
>          Title: OOo installation for smoketest/subsequenttests
>      Posted by: [email protected]
>       Affected: -
> Effective from: DEV300 CWS sb118
>            CWS:
> <http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300/sb118>
>     CWS status: ready for QA
> 
> 
> *Summary*
> --------
> + instsetoo_native always builds openoffice_en-US.archive
> 
> + smoketestoo_native installs it to solver directory "installation"
> 
> *Description*
> -------------
> Building module instsetoo_native now always creates an
> openoffice_en-US.archive installation set, in addition to whatever
> else is built there.
> 
> Building module smoketestoo_native extracts (or re-extracts, if the
> tarball is newer) that openoffice_en-US.archive into the solver, to a
> new directory "installation".  (So that the smoke test and any
> subsequent tests, see
> <http://www.openoffice.org/servlets/ReadMsg?list=interface-announce&msgNo=1266>,
> have easy access to an OOo installation to test against; see
> <http://wiki.services.openoffice.org/wiki/Test_Cleanup>, which is
> currently under construction.  On Windows, file paths into the solver
> would be too long, so on that platform for now each test extracts its
> own OOo installation into a temp directory and discards it afterwards.)
> 
> A consequence of this is that smoketestoo_native no longer checks any
> of the non-archive, native installation set package formats.

One more detail I forgot to mention:  To manually execute the smoke test 
(by loading smoketestdoc.sxw and clicking its "start smoketest" button), 
one must now load smoketestoo_native/$INPATH/bin/smoketestdoc.sxw 
(copied there by smoketestoo_native/makefile.mk) instead of 
smoketestoo_native/data/smoketestdoc.sxw.  Otherwise, the Basic test 
code in the document will not find the TestExtension.oxt next to the 
document, and the extension tests will fail.

-Stephan