* So you are basically trying to test i18n (Internationalization) because more than one language not L10n(localization)
* I often play around with what you are looking for in my day in day out job. What we look for is ---
* Users have a regional settings set up in the application, for example when user A log in userA should see
* the application in ja where as when userB log in userB should see the application UI in cn(Chinese).
*
* Use case for i18N automation
* 1. Verify welcome message on UI after user login
* 2. Verify error messages
* 3. Verify tooltips
* 4. Verify common webelements like button/ dropdown etc
* 5. Verify the email template, some application has a predefined email template to send mails/ if any translation service
* 6. Verify welcome message on UI after userA login, userA log out immediately followed by UserB login, to check whether browser
* cache holds the previous translation (should not)
* 7. If your database is UNICODE check for data as well.
* 8. If the application User_Name honors Region/ timezone check that as well
*
*/
// just talking about the Selenium part , though there is more to it, you can do something like
package snadbox;
public class i18N {
static String HOME_PAGE_TEXT = "国際交流基金(ジャパンファウンデーション) ";
public static void main(String[] args) {
// TODO Auto-generated method stub
if ("国際交流基金(ジャパンファウンデーション) ".equals(HOME_PAGE_TEXT)) {
System.out.println("String correct");
}
}
}
No comments:
Post a Comment