my 2c:
I would assume the assumption behind /"no need to run tests in localized
instances"/ idea is (beyond the oh so short-sighted
"we-got-deadlines-to-keep" argument) that localizing does / can not
break the product.
Either this is true, but then repeat tests by different persons,
approaching the product in some novel, unexpected ways, may/will dig out
some errors
Or the hypothesis has been proven wrong based on experience with
language X/env Y, so let's test whatever combination we can
The reality is probably in between somewhere. In any case the more
flying hours before the launch the better.
smo
André Schnabel wrote:
Hi Jörg,
Joerg Sievers schrieb:
Hi Andre,
Andre Schnabel wrote:
I used to run the *_upd.bas tests per module. If there are more
tests than that, please tell (maybe at next weeks IRC meeting ;-) ).
in each modul _all_ tests need to be run. All *.bas files.
If there is an old, unsupported test it should be removed in CVS
branch by maintainer of the test (see description in .bas) file.
I thought, the answer is something like that. Excuse me, but thinking
of the recent discussions and knowing that many of the tests will fail
in localized environments.
All the discussions about localized testing make me wonder. At the one
hand we are told, that functionality doesn't need to be tested in a
localized environment. SBA stressed the question "what *not* to test"
in the last IRC meeting.
At the other hand I now hear that we would need to run all the tests.
Imho both of this statements cannot be true at the same time.
I hope, we can sort this out.
André
---------------------------------------------------------------------
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]
