tekom-Jahrestagung 2012 - ActiveDoc

Lokalisierung und Übersetzung / Localization
Testable) or similar, localization must be a negotiable, continuously
responsive and evolved department in line with the corporate culture.
For all the emphasis on de-regulation and adaptivity, Agile is actually
a fairly well-bound field with a set of principles that can be replicated
throughout projects.
Why is this important? Partly, because a better representation will aid
in the integration of accurate localization QA services in the software
development mainline and save effort at an early stage that would
eventually go in the test pipeline and allows you to establish a good test
strategy that involves all four levels of software development: planning,
implementation, regression and deployment.
User Stories as engine
of adaptation
Integrating automated
and manual testing
Asserting Test Strategy and Matrixes
When creating a test strategy, you have to accurately define the QA processes
and their integration in the lifecycle. An early involvement and
understanding of specs, requirements and the product scope will feed
the production of an accurate test matrix, complete with pre-assumed
configurations and locales, starts at the User Story creation level, where
the product scope actually materializes.
At its drafting, the User Story already needs to integrate localizability
and internationalization concerns, by way of specific linguistic and
functional testing. These criteria are an integral part of the final acceptance
process and the successful implementation of the User Story must
be predicated on its fulfilment.
The test strategy also has to take into account the responsibility when
decentralizing that comes with Agile practice: the contact points can
be multiple and, in case of dedicated testing teams, the syncing between
the localization functionality testing team and other functionality
teams must be carefully established in order to avoid discrepancies or
redundancy.
Localization Testing Methodologies
Another issue is that regression must be mitigated through unit testing
and automation as early as possible. Given the tight timelines involved
in Agile development, preliminary localizability testing must be done in
advance before the implementation of the User Story in order to reduce
effort with later regression and workflow adjustments.
The implementation of different testing methodologies depends on the
resource availability and the project needs. On the tool level, an integrated
test and development environment, as well as common issue
tracking systems, is a pre-requirement for valid reporting, as well as the
configuration and implementation of specific automatic testing.
Specifically, automation is essential on the source code level, where
the semantics of string implementation are initially checked. In a testdriven
development environment, development unit tests are routinely
run during program compiling and building, and can already provide
reports on missing and incorrectly implemented application strings.
Automation can also assist with specific user interface issues, as well as
functional text issues such as script rendering, blacklists and hotkeys.
204
tekom-Jahrestagung 2012