Comments on: Localization Testing – Part II http://www.testingmentor.com/imtesty/2009/11/18/localization-testing-part-ii/ Treatises on the practice of software testing Tue, 07 Feb 2012 09:15:11 -0500 hourly 1 http://wordpress.org/?v=3.1.3 By: testingmentor http://www.testingmentor.com/imtesty/2009/11/18/localization-testing-part-ii/comment-page-1/#comment-338 testingmentor Thu, 10 Dec 2009 15:41:08 +0000 http://testingmentor.com/imtesty/2009/11/18/localization-testing-part-ii/#comment-338 Hi Anuj, Yes, I didn't mean to imply testers didn't need to know anything about what they are testing. The more testers know about the 'system' they are testing the better they will be able to test and identify issues. I also think if testers understand the system more they will also be able to figure out ways to automate tests that might identify problems as described more efficiently and effectively. Hi Anuj,

Yes, I didn’t mean to imply testers didn’t need to know anything about what they are testing. The more testers know about the ‘system’ they are testing the better they will be able to test and identify issues.

I also think if testers understand the system more they will also be able to figure out ways to automate tests that might identify problems as described more efficiently and effectively.

]]> By: Anuj Magazine http://www.testingmentor.com/imtesty/2009/11/18/localization-testing-part-ii/comment-page-1/#comment-337 Anuj Magazine Thu, 10 Dec 2009 06:50:25 +0000 http://testingmentor.com/imtesty/2009/11/18/localization-testing-part-ii/#comment-337 I agree with you on the first part when you say simple automation could save such kind of errors. Infact, this is what was done to rectify the situation. Largely, i think having an understanding of characters and other nuances that assists to distinguish between language is not a bad skill to have. It can definitely help a tester observe something upfront and report if any of the earlier processes are broken. Regards, Anuj I agree with you on the first part when you say simple automation could save such kind of errors. Infact, this is what was done to rectify the situation.
Largely, i think having an understanding of characters and other nuances that assists to distinguish between language is not a bad skill to have. It can definitely help a tester observe something upfront and report if any of the earlier processes are broken.

Regards,
Anuj

]]> By: testingmentor http://www.testingmentor.com/imtesty/2009/11/18/localization-testing-part-ii/comment-page-1/#comment-335 testingmentor Thu, 10 Dec 2009 01:08:55 +0000 http://testingmentor.com/imtesty/2009/11/18/localization-testing-part-ii/#comment-335 Hi Anuj, This type of error doesn't require familiarity with languages. This is one of the types of problems that should have easily been caught by an effective build verification test suite. A simple automated test could verify the correct resource files are being built into the appropriate language verion in about .25 seconds. Checking for 'certain characters' could also be automated by looking fof language specific characters in the resource files. However, this is a highly risky approach to testing and is likely to throw a lot of false positives. Hi Anuj,

This type of error doesn’t require familiarity with languages. This is one of the types of problems that should have easily been caught by an effective build verification test suite. A simple automated test could verify the correct resource files are being built into the appropriate language verion in about .25 seconds.

Checking for ‘certain characters’ could also be automated by looking fof language specific characters in the resource files. However, this is a highly risky approach to testing and is likely to throw a lot of false positives.

]]> By: Anuj Magazine http://www.testingmentor.com/imtesty/2009/11/18/localization-testing-part-ii/comment-page-1/#comment-333 Anuj Magazine Wed, 09 Dec 2009 06:16:35 +0000 http://testingmentor.com/imtesty/2009/11/18/localization-testing-part-ii/#comment-333 It is always a good practice for a test engineer to understand the differences between similar looking languages. I had an example in the past experience when for a German version of a product, the UI started showing up in Spanish on update because of a bug in the system (possibly German UI referencing wrong resource file). Test Engineer while testing could see the text in Non English language but could not verify if it was really German or Spanish. As majority of Globalization testing is done by Non Language experts, it is always ideal to add to testing checklist- certain characters that you would look in the UI to ensure the presence of correct language under test. It is always a good practice for a test engineer to understand the differences between similar looking languages. I had an example in the past experience when for a German version of a product, the UI started showing up in Spanish on update because of a bug in the system (possibly German UI referencing wrong resource file). Test Engineer while testing could see the text in Non English language but could not verify if it was really German or Spanish. As majority of Globalization testing is done by Non Language experts, it is always ideal to add to testing checklist- certain characters that you would look in the UI to ensure the presence of correct language under test.

]]>