Testing Localization

Testing Localization in ScratchJr

Notes

• The threshhold for adding a new language to the ScratchJr app is 100% (all strings need to be translated)
• We get the translation files from transifex ** The files will have the correct json structure ** However, mistakes (typos, transpositions, misunderstanding of format) by translators can cause issues with functionality in the app

What to test for each ScratchJr release

Test the most important/ most used workflows

• Test a few popular languages, a few right-to-left languages (when they have been added to ScratchJr), and a few non-Latin-alphabet languages (Khmer, Chinese, etc.) for each release using the most important workflows

What to test when a new language is added to ScratchJr

Test a couple of representative things from each group of items on each page

• Create a new project ** The title should be “project-n” which should be translated
• Click on a couple of characters from the library ** Their names should be translated ** You should be able to add at least one to a project
• Click on a couple of backgrounds from the library ** Their names should be translated ** You should be able to add at least one to a project
• Check some sample projects ** They may have strings in the project that could break project if incorrectly formatted, etc. ** Check Farm, Seasons, Playing soccer/ Friends ** The project should load ** The green flag should work to play the project
• Check the About page (book icon) ** It should load ** The number tags should work (in the diagrams)

TODO: Open questions

• How should we deal with string length that overflows ScratchJr containers? ** The containers were designed to fit English strings
• Are there languages where a significant portion of people would be more comfortable with the numerals used in that language than with Arabic numerals? ** If so, should ScratchJr change anything to accommodate other numerals?
• Create a page for Most Important Workflows test cases