This page describes the general test procedure for L10N teams and related test cases.
- Find translation mistakes
- Find translated strings that remain in English
- Find strings not marked for translation
- Test keyboard support for different layouts
The L10N teams might use the L10N Results Template in order to guide the members on how to test each package. Each team can choose a priority of testing but we recommend a special attention for Anaconda, the Fedora installer. Testers also might prioritize the modules listed for the next Fedora release in Transifex.
While testing Anaconda strings we strongly advice the concurrent test of keyboard layouts in order to help I18N testing. The related tests cases are available at Category:I18n_Installation. The collaboration of testers who have keyboards models others than qwerty are highly appreciated.
Specific L10N bugs like typos and translation mistakes should be directly reported to the local translation team mailing list or a bug report should be filed at Bugzilla against the related language. General bugs that affect all languages like strings not marked for translation, downstream patching that breaks translations and input method issues should be filed against the related package.
Test days could be held for L10N specific issues or along with I18N members in order to increase tests coverage. L10N and I18N related test days will be announced at the L10N, I18N an QA mailing lists.