英语论文网

Internationalizing testing? The title is deliberately chosen—
internationalizing testing. The idea is to internationalize all software testing instead of developing a separate testing process and calling it in 代写留学生论文/留学生论文代写ternationalization testing.
Internationalized testing is not the same as localization
testing. In internationalized testing, product functionalityand usability are the focus. Localization testing is forlinguistic relevance and for verification that functionality hasnot changed as a result of localization.Does this sound familiar? Some companies avoid internationalizationtesting and internationalized testing for any number
of reasons. Product groups don’t think about internationalizationat all. Or they think that internationalization testing isperformed by “some other group.” Or they just don’t thinkinternational is very important. Many test groups don’t knowhow to test for international and have no resources to helpthem learn how.
Admittedly, there is not much information specificallygeared to internationalization testing. For example, inresearching this article, I found that only the most superficialinformation is publicly available. So, it’s no wonder peopledon’t understand the process. Of course, this article can’tcover everything you need to know, but I’ll try to touch on asmany areas as possible.Some companies do have internationalization in place,but often the testing is not adequate to catch enough of the
internationalization problems, and it’s frequently done too late
in the quality assurance (QA) cycle for fixes to be integrated
into the product.
I hope to remove most of the FUD — Fear, Uncertainty and
Doubt — about internationalizing test suites in the course of
this article. It seems that a lot of testers don’t think that they
can test international specifications and data; they think it’s
too “hard” or that it will take a long time to learn. The reality
is that if the information is presented in a clear, straightforward
way, it is very easy to learn. Once testers have done a
small amount of internationalized testing, they’ll feel like it’s a
regular part of the testing repertoire.
By internationalizing existing tests, including all testers, and
eliminating redundant areas, more of the product internationalization
can be covered with the same number of people in
the same amount of time. I’ll provide some guidance on ways
you can get more coverage with the resources you have.
IS ENGLISH A BASE TEST?
Much of the software testing today is conducted as though
US English is a sort of base or core test, and other locale formats
and language characters are added functionality. But
consider how the product is developed. Properly internationalized
products are designed and coded with internationalization
in mind. The internationalization in the code is everywhere,
not in one or two modules. In fact, for most products
it would be impossible to have separate internationalization
modules installed alongside existing code to “perform internationalization
functions.” The test design is no different. Test
plans and suites must be internationalized the same way program
design and code are.
English is written in ASCII, and ASCII is a direct subset of
all major charsets. So no matter which charset you’re testing,
you automatically test ASCII. Therefore, testing English
(ASCII) alone is a waste of time. The same is tr