puma brand shoes 2139

[nikeshoes6i]

Best Practices in Localization Testing and Testing Process
Localization testing has gained a lot of momentum and market share in the recent years, thanks to ISVs who focus on global launch of their products where ��time to market�� is an important criterion. Often ISVs lack time in their testing phase for the English version, leave alone the localized versions. In such situations, how can the ISV or a testing service provider add value to the localization testing phase and not compromise on quality? Here is where one needs to focus on the best practices in the localization testing phase, which helps ship the product on time and provide the required coverage. Here are a few core best practices especially applicable to localization testing:
Build Reusability �C Reusability bears a lot of importance in localization testing because there is a lot in common between pseudo localization testing and localization functional testing. Test cases for pseudo localization testing can be largely reused in localization functional testing. Test data in pseudo localization phase would either be gibberish or typically a representative language such as German,puma brand shoes, whereas in the localization testing phase, you would be testing with data for every single locale. Reusing previously written cases saves a lot of time and effort and gives you good test coverage. There are quite a few differences between pseudo loc and loc testing phases (for more details on this refer to my previous blog titled ��Why take on localization functional testing when you��ve already done pseudo localization testing? ��,buy nike air max shoes, at http: //www. qainfotech. com/blog/2010/01/why-take-on-localization-functional-testing-when-you%e2%80%99ve-already-done-pseudo-localization-testing/
We should look at building generic test cases for pseudo localization and localization functional testing by classifying products �C such as localization testing for e-commerce applications, for social networking applications etc. This will expedite boot strapping localization testing for such projects as we��ve built reusability in test case design upfront. Your testers can take on such tasks after project completion, during down times.
Exercise diligence in filing localization bugs �C A Localization bug may differ from the core product bugs in English. It may be specific to the language or group of languages under test. Tester should apply attention in isolating the bug and help the developer comprehend the issue quickly. This is also similar to bugs specific to OS Browser testing. Based on the nature of the bug, the tester should decide whether to report all issues or file separate bugs for each issue. Combining issues and providing details such as platform on which the issue was observed, screenshots, steps may help in resolving the bug quickly.
Build a comprehensive yet optimized matrix to test �C Building a matrix in localization testing is important since the variables to test are large. In fact, building a matrix here is more complicated than in OSB testing since localization testing touches upon both OSBs and locales under test. You can talk to the product management team to ease your work in such a scenario. Understand launch priorities of various markets including market share, targeted number of end users in each market, launch timelines etc. Also take into account the OSB usage specific to the target locale. For example a given browser that has a large global market share, may not have a significant share in the target locale. Such inputs will help you prioritize the OSBs to test on for various locales. Web sites such as: http: //marketshare. hitslink. com/, will help keep track of OS Browser usage statistics.
Automate the right set of test cases �C Reusability is possible between pseudo localization and the localization testing phases. Set aside some time for automation in the pseudo localization testing phase which can be re-used in localization testing. Test data should be localized for automation. This would provide the tester a lot of time to focus on exploratory testing. Do not spend a lot of time automating UI tests, as that is best done manually especially in localization testing. Picking functional test cases to automate would provide maximum reusability not just during the localization testing phase,north face, but also during the product maintenance phase.
Use of productivity tools �C Preparation of test data is especially time consuming in localization testing. To make this test process simpler, more accurate and faster, a number of open source and freeware productivity tools are available. A smart tester uses such tools to help expedite the test process. They can be downloaded and shared in the internal knowledge base system. Some examples of such tools are: keyboard simulators (Microsoft keyboard layout creator,canada goose outerwear, Java virtual keyboard).
Adopting the above defined practices will not only help you meet time crunched deadlines but also create a robust localization testing methodology to practice and improvise across projects. This is in no way intended to be a comprehensive list of best practices, but rather a good set to start adopting right away. Happy Localization Testing!
For more information: http: //www. qainfotech. com
Topics related articles：


1855

article15227

5979