smoketest and assertions

Hi,

starting with m103, the next build on the DEV300 codeline, in
non-product builds [1], the smoketest in smoketestoo_native will break
on assertions.

That is, *any* assertion (no matter whether from the tools or the sal
diagnostic system) raised during the actual smoketest, or during startup
or shutdown of OOo, will make the test fail.

Since a successful smoketest is a release criteria for every milestone
build, this means that milestones can't be released if a CWS introduces
new assertions (during office startup/shutdown and the actual smoketest,
that is).

So, you're strongly encouraged to build a non-product version of your
CWS, and run the smoketest, before passing the CWS to QA.

Even better, you're strongly encouraged to *work* with a non-product
version of your CWS during your daily development: Assertions point to
bugs, so introducing new assertions means introducing new bugs, and
that's something you surely want to avoid, anyway.

Ciao
Frank

[1] http://wiki.services.openoffice.org/wiki/Non_Product_Build

-- 
ORACLE
Frank Schönheit | Software Engineer | [email protected]
Oracle Office Productivity: http://www.oracle.com/office
--
-----------------------------------------------------------------
To unsubscribe send email to [email protected]
For additional commands send email to [email protected]
with Subject: help