On 7/26/07, Thorsten Ziehm <[EMAIL PROTECTED]> wrote:
Caio Tiago Oliveira wrote:
> l10n tests on TCM would help to find these cases.
How should the test case look like?
For new functionality, we would have the same kind of test we have for
the current.
We could add a new testcase creating a report using the report
designer (I run out of ideas because I haven't used it yet).
> In general, it's nice to review the new strings before releasing.
+1
We could got a list from the l10n team, telling the menus and dialogs
involved on the new strings.
Sometimes it's hard even for the localizers to find the string he is
translating on the UI, even following the tips (as the name of the
key, the context, etc.).
The test itself would be to open them and look they're correctly translated.
I don't know if the people coordinating translation inside Sun already
have such info at hand, but would be nice to get it.
The TCM testcase itself would be a list of places to check.
These testcases would change on a release base, so it's a bit more
dynamic than this TCM is suitable for, but it's possible[1].
We could create a new scenario for this, adding and removing testcases
on demand.
The timeline (and life cycle) of these testcases would be the same as
of the our ordinary TCM l10n testing.
Truly speaking, these are the places more likely to find l10n issues
on a minor release base.
1 - I just got a wish to the opensource TCM.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
