SwissChecklist

Checklist: Software Development - Control Translated User Interface

Multilingual software often misses some language components in some translations. This checklist helps you to remember everything. It is used for testing the UI as a user, not for validating the code or language tables. I recommend that you use this checklist for every module/component separately.

  • Test Specs

    Show Details Show Substeps Show Substeps Show Substeps

  • Module to test

    Show Details Show Substeps Show Substeps Show Substeps

  • Language/Culture to test

    Show Details Show Substeps Show Substeps Show Substeps

  • Standard UI

    Show Details Show Substeps Show Substeps Show Substeps

  • Look at every visible button and label, things that are usually remain the same during the entire runtime of the software

    Show Details Show Substeps Show Substeps Show Substeps

  • On every button, verify that the mouse-over text is translated

    Show Details Show Substeps Show Substeps Show Substeps

  • Check that dates are in either the cultural format, or an error-free format

    Show Details Show Substeps Show Substeps Show Substeps
    ISO Standard Error Free Format
    4DigitYear-2DigitMonth-2DigitDay
    this format works everywhere, because no culture uses this format with reversed month/day
    • 2010-04-23 (wrong: 10-04-23)
    • 0032-04-03
    • 2100-02-01

  • Check automatically appearing help text (like AJAX-bubble text)

    Show Details Show Substeps Show Substeps Show Substeps

  • Check Symbols/icons/colors for cultural appropriateness

    Show Details Show Substeps Show Substeps Show Substeps

  • Check Abbreviations if they are understandable

    Show Details Show Substeps Show Substeps Show Substeps

  • Check techno-talk (sometimes english words like "Workflow" are used in other cultures, but non-IT-users don't understand them)

    Show Details Show Substeps Show Substeps Show Substeps

  • Error-Handling

    Show Details Show Substeps Show Substeps Show Substeps

  • Check date input methods, if the cultural default works (or click only)

    Show Details Show Substeps Show Substeps Show Substeps

  • Test all error scenarios, if the error message is in the right language

    Show Details Show Substeps Show Substeps Show Substeps

  • Help / documentation

    Show Details Show Substeps Show Substeps Show Substeps

  • Test all immediate help texts (like what appears on F1)

    Show Details Show Substeps Show Substeps Show Substeps

  • Test all default help text (documentation)

    Show Details Show Substeps Show Substeps Show Substeps

  • Test links in the help, if they go to the right language

    Show Details Show Substeps Show Substeps Show Substeps

  • Test images in the help, if screenshots are the right language or at least understandable

    Show Details Show Substeps Show Substeps Show Substeps

  • Hidden UI

    Show Details Show Substeps Show Substeps Show Substeps

  • If there is a hidden admin-interface, test that too, according to all tests above

    Show Details Show Substeps Show Substeps Show Substeps

  • New Step

    Show Details Show Substeps Show Substeps Show Substeps
Use this Checklist

Preview/Print

Use

Change

Sort

Delete Template