Unreferenced date June 2009 Pseudolocalization is a software testing method that is used to test Internationalization and localization internationalization aspects of software. Specifically, it brings to light potential difficulties with localization by replacing localizable text particularly in a graphical user interface with text that imitates the most problematic characteristics of text from a wide variety of language s, and by forcing the application to deal with similar input text. If used properly, it provides a cheap but effective sanity test for localizability that can be helpful in the early stages of a software project. Rationale If software is not designed with localizability in mind, certain problems can occur when the software is localized. Text in a target language may tend to be significantly longer than the corresponding text in the original language of the program, causing the ends of text to be cut off if insufficient space is allocated. Words in a target language may be longer, causing awkward line breaks. In addition, individual characters in a target language may require more space, causing Diacritic modified characters to be cut off vertically, for example. Even worse, characters of a target language may fail to render properly or at all if support for an appropriate font is not included. This is a larger problem for legacy software than for newer programs. On the input side, programmers may make inappropriate assumptions about the form that user input can take. Method For small changes to mature software products, for which a large amount of target text is already available, directly testing several target languages may be the best option. For newer software or for larger user interface changes , however, waiting for text to be translated can introduce ... UI text early in the development cycle, as it might change and need to be retranslated. Here, pseudolocalization ... pseudolocalization has the advantage of the translated strings featuring the characteristics specific ... more details
saved book title Software testing subtitle cover image cover color Software testing Introduction Software testing Black box testing Black box testing Exploratory testing San Francisco depot Session based testing Scenario testing Equivalence partitioning Boundary value analysis All pairs testing Fuzz testing Cause effect graph Model based testing Web testing Installation testing White box testing White box testing Code coverage Modified Condition Decision Coverage Fault injection Bebugging Mutation testing Testing of non functional software aspects Non functional testing Software performance testing Stress testing software Stress testing Load testing Volume testing Scalability testing Compatibility testing Portability testing Security testing Attack patterns Localization testing Pseudolocalization Recovery testing Soak testing Characterization test Unit testing Unit testing Self testing code Test fixture Method stub Mock object Lazy systematic unit testing Test Anything Protocol XUnit List of unit testing frameworks SUnit JUnit Concutest CppUnit Test More NUnit NUnitAsp CsUnit HtmlUnit Test automation Test automation Test bench Test execution engine Test stubs Testware Test automation framework Data driven testing Modularity driven testing Keyword driven testing Hybrid testing Lightweight software test automation Testing process Software testing controversies Test driven development Agile testing Bug bash Pair Testing Manual testing Regression testing Ad hoc testing Sanity testing Integration testing System testing System integration testing Acceptance testing Risk based testing Software testing outsourcing Tester driven development Test effort Testing artefacts IEEE 829 Test strategy Test plan Traceability matrix Test case Test data Test suite Test script Test harness Static testing Static testing Software review Software peer review Software audit review Software technical review Management review Software inspection Fagan inspection Software walkthrough Code revie ... more details
Encyclopedia
top
