Hi Alex,
for the l10n versions, we (Globalization) do perform TCM l10n testing.
All results are very transparent and you can see them here:
http://www.sunvirtuallab.com:8001/tcm2/opensource/tcm_report.cgi?tcm_config=newooo&action=report_list&project_id=23
On this list we always announce when we start TCM testing so that
everybody interested can join the testing.
As for the Sanity Check tests, if these are insufficient you are very
welcome to contribute to put together a better set of sanity check test
cases that better serve your or other purposes. This is also why we
migrated to this new TCM, because it give us all the possibility to
create test scenarios to be able to sufficiently test the various
versions based on time and resources.
Just let me know if you have any other questions,
Rafaella
Alex Thurgood wrote On 11/16/06 11:56,:
Andre Schnabel wrote:
Hi André,
Jörg just put the information on the wiki page, what automated tests
are run. Each native lang team is encouraged to run a full set of
manual Tests. Everybody is envited to run automated tests and report
the bugs.
So "run only sanity tests" can never be the base for a GO/NOGO decision.
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 ?
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
