Hi Christian,
Christian Lohmaier a écrit :
Hi Sophie, *,
On Tue, Jun 30, 2009 at 9:53 PM, Sophie<[email protected]> wrote:
Christian Lohmaier a écrit :
On Tue, Jun 30, 2009 at 5:45 PM, Frank Schönheit - Sun Microsystems
Germany<[email protected]> wrote:
[...]
The problem is not that the smoketest wasn't performed. The problem is
that someketest_oo did run without problem. It doesn't do an
installation as the user does/starts OOo in another environment the
user would do.
smoketest_oo native just runs and reports success in both cases.
From what I know, a comparison between cws and mws tests if they are not run
in the exactly same environment will not provide reliable infos so the
community is out of scope here, or did I miss something?
Maybe it wasn't clear enough - smoketestoo_native is not using
testtool or doing manual tests - This is a very short test that can be
done as part of building OpenOffice.org.
Maybe a bad name, since the former manual testing instructions were
also labeled "smoketests"
It consists of installing OOo into a temporary location, runnning OOo
and creating files from every app (writer, calc, impress...) - I
didn't have a closer look as to what else it does. But that it didn't
catch the installation issue is really sad. So we had a released
milestone that the user could not even launch.
I wanted to give it as an example that automatic testing cannot find
everything, not even obvious bugs because it does stuff differently
than a user would do. That even when the test says "OK", trying to use
the same functionality can cause a crash in real world.
(another example if the test would check PDF-export by exporting an
empty document without text, it would not have detected the Bigendian
PPC crasher - so you did check PDF export, but not with the necessary
circumstances to trigger the bug)
I was not aware of those tests, thanks for the explanation, and... I
won't be curious enough to try to run them ;)
Kind regards
Sophie
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
