tekom-Jahrestagung 2012 - ActiveDoc

Lokalisierung und Übersetzung / Localization
Hybrid testing with automated and manual approaches can also highlight
specific problems in the user interface, where the control layout is
somehow flawed or incorrect, or the rendering of the character locale,
especially on bidirectional languages. This method is particularly suitable
to in-context review, unlike the more typical screenshot review.
Moreover, it avoids the time-wasting meanderings of exploratory testing.
Test coverage and test
plan optimization
Types of testing
Continuous deployment
and testing
Localization Testing Domains
An optimal test coverage can only be achieved with the replicability of
test cases and integrational strategies between all departments involved
with software ergonomics, localization and development. It is also critical
that all testing effort is linked to correctly prioritized User Stories
with their own specific test cases. This will enable the testing to concentrate
and focus on user-critical areas of the application. It will also allow
for more effective effort management.
Test cases should be preferably structured according to the priority of
the User Stories but, in the context of an iteration development, they
should reflect primarily the localization acceptance tests for the User
Stories ranging from three basic domains: cosmetic, functional and
linguistic.
Linguistic testing relies mainly on prescriptive reference materials
(such as glossaries and style guides) and checks for typographical,
grammatical, and contextual errors. Given that text in the application is
just one more element of its visual design, special attention should be
given to cosmetic guidelines that are shared amongst the team, and especially
between design and development-oriented staff. These guidelines
can include the optimal distance between elements, color combination
palettes (which are also culturally determined) and fonts. Testing
should commence as soon as possible on the new strings, which implies
that a tight integration with your LSP and automatic machine translation
are also solutions to be carefully assessed in order to fulfil multilingual
requirements in the context of a 2 or 4 week iteration.
Solidifying the Testing Loop
Agile focuses on usability that brings value to the end-user, so localization
testing should primarily focus on helping to deliver this value, as
it is defined in the product scope by the stakeholders. In a continuous
deployment environment, the emphasis should rely on preventing the
occurrence of problems and reducing regression costs, so pre-planning,
early engagement and a solid communication flow are key to the testing
process. Testing is not a separate focus, but rather an essential component
of everyday methodology, and the organic feedback loop between
result, assessment and adjustment enforced by Agile can be a powerful
tool for producing quality multilingual software prepared for the demands
of a global market.
If you have any questions please contact: alberto.viralhadas@gmail.com
tekom-Jahrestagung 2012
205