Skip to content

How to Test the App's Translations in Chrome

julianrkung edited this page May 9, 2021 · 1 revision

This document will detail how to test the app's translations in Chrome. It will cover how to efficiently test in a development environment as well as in production.

Testing Translations in an Development Environment

  1. To test your translations in a development environment, we recommend changing the detectLanguage function in src/lib/i18next to always return "my". This is what navigator.language returns in Chrome if your default language is set to Burmese. After refreshing, text containing translations should be translated to Burmese.

image

Testing Translations in a Production Environment

To test translations in a production environment, you'll need to temporarily set your browser language settings to Burmese. The following procedure will detail how to do this for Chrome.

  1. Open your browser's settings page. You can do this by clicking the top right triple dot icon and hitting "Settings" image

  2. When on the "Settings" page, search for "Language" and click the dropdown to expose a section labelled "Order languages based on your preference" image

  3. Press "Add Language" and select "Burmese" if it not already there. Then, put "Burmese" as the top choice so that it's the most preferred. image

  4. (Optional) Open an incognito window and navigate to https://meepanyar.netlify.app and make sure that the app is translated image

  5. Once finished testing, make sure to move "English" (or whatever language was originally your most preferred) back to its original spot.