Planning for Testing and QA
From IndLinux
Contents |
Background Information
Since the founding of IndLinux project to enable GNU/Linux, the procedure for localization has resulted in quick short term results. There was very few formalized procedure's for quality assessment of the code as well as of the translation's, then there were little understanding of user requirement. This discussion would like to explain how the testing process in a collaborative environment. I strongly consider the process requires something more than an unified Automation Framework like LDTP, Dogtail to meet the language specific issues.
Setting up a Test Lab.
This would consist of Native language OS and browsers Testing tools, viz. pretty much challenging to find tools that support Indian language's. Testing should be modularized into User Interface testing and Input/ Output testing. Unicode enabled spreadsheet, db etc..
Language Specific Testing
Not only Indic language's but also other language's with complex scripts like chinese, korean , vietnamese would be challenging, the whole test framework would require the following test to take place. The test's could be broken down into::
- Functional testing
During this phase, the developers would come up with a clear spec, testing in parallel with the base english system, come up with use-case scenario's to check for missing features. Decisions on encoding etc.
- Automated testing
LDTP, is a Keyword Driven and a unified automation framework of Novell, solves the problem with little language-specific issues, its somewhat similar to Rational Robot, This phase would be a bit labor intensive and complicated which would involve in creating Data and manually localizing test scripts and also testing to see if the tools we use support the target encoding. Checking whether the product UI is been translated.
Dogtail, is another option for Test Driven development, although it varies quite a lot from LDTP by design, its another popular tool for Automated testing
- Linguistic Testing
Here again dealing with language specific's cases like testing the acceptance of input characters and translation checks [testing it with pseudo-translation's]. the testers must be familiar with computer terminology.
- Locale Testing
Currency, Date/time, Payment's .....
- Web testing
Browser's, Fonts, Graphical test
Backing up the Test suite
A bug tracking system with which is unicode enabled, attachment
