Hi Alex,
And that is a good thing, but it was unfortunately exactly what we did
for 2.0.4 - based our decision on TCM sanity tests alone, at least for
some platforms and for some languages, unless of course I am unaware of
general qa testing that was done elsewhere, e.g. internally by Sun.
This begs the question that if the qa for a given version / language
combination is done internally (e.g. with the qa testtool), why bother
doing sanity checks at all ?
that's a good question.
When looking at the automation test matrix of those builds that are
checked by Sun QA engineers
see http://wiki.services.openoffice.org/wiki/OOoRelease1AutomationTestMatrix
you have to regard that these builds get checked against a StarOffice
build that is based on the same development environment which is used to
build OpenOffice.org builds. Mostly both applications share a big part
but some little things (eg. the linguistic module) are different.
Additionally you need to keep in mind that these 16 localizations
represent just a subset of all localizations that are available as
language packs (see the full list of languages planned for 2.1 here:
http://wiki.services.openoffice.org/wiki/OOoRelease205). At least the
localizations that use language packs need to be checked very well. In
rare cases it can happen that the application can crash if there's a
problem within a resource file of that language pack.
...and the more people involved into the QA process the better it is....
Kind regards, Joost
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
