Measurement and best practices of i18n and l10n testing (2)

To better measure the i18n and l10n testing efficiency or the i18n and
l10n quality, it's very critical to do the following things:

1. To use standard keywords for different kind of bugs, the keywords
should be in a easy to understand and remember convention, such as
i18n-external, i18n-internal, l10n-external, l10n-internal,
g11n-external, g11n-internal, there shouldn't have too many keywords
like language specific or team specific unless it's really necessary.

2. Don't use i18n/l10n specific subcategories unless it's really
necessary, especially the i18n subcategory since i18n problems should
be part of the core problems, not problems of an additional feature.

3. To follow standard definitions of the bug priority and severity, so that the nubmers of P1, P2 or P3 bugs do make sense.

4. To generate metrics frequently (automatically) to compare progress
or trends among products, releases, teams, etc. Then to leverage best
practices from those who do the best or find the root causes and
develop an improvement plan for those who do the worst.

Posted at 02:28PM Oct 30, 2006 by byuan in Globalization  |  Comments[0]