Hi Caio,
Caio Tiago Oliveira schrieb:
I might to be oversimplifying this, but...
there are a lot of new strings or dialogs.
The same way as the l10n tests are made for the functionality we have
today, there is the need to add *l10n* test sometimes.
Thanks for this plain and simple answer. This is what l10n tests are
about: test, if the localization (includinf new strings) is correct.
Speakinf for myself - I have translated approx 1000 words for 2.3 and
reviewed several 1000 translations. In many cases I had just the english
text in the translation file - no Idea what functionality it belongs to,
no idea, where the string is used in the UI ..sometimes no Idea, if the
String would fit in the current place.
We might have done several mistakes and therefore the CWS should be
tested. I really do not understand the discussion that no tests should
be done.
@Thorsten - we agreed, that l10n testing is not about functionality in
the first place - but feature testing is a side-effect of l10n testing.
(Sophie is right, that many people are not interested in testing any
build that is not in their own language)
@Mechtilde - I would not say, that German is one of the "rock solid"
languages for OOo 2.3. This is the first time, that German is not a
source language but a translation like all other languages. We had
a CWS test for that and maybe people are already using Pavel's builds,
that behave that way ..but I don't think, we should deny testing befor
we asked, if someone is willing to do the tests.
I see, that there is a problem - we have no test cases for those
newstrings in TCM ... but most of us know where the new strings came in
.. build a wiki page with those areas and tell people to have a look at
those.
(List of new features is agood staring point for that).
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
