An Organic Mechanism

1. AnOrganicMechanism EffectiveLocalization QA inAgileDevelopmentEnvironments

2. PART I AgilePrinciplesinLocalization

3. TESTING AGILE WORKFLOW Agilelocalization • Fast response to changingrequirements • Collaborative • Shorterdeploymentperiods • Betterworktracking • Betterprojectintegration

4. TESTING AGILE WORKFLOW Agileemancipates TEAMS… BUT miscommunicationandunclaritycompromiseresults.

5. TESTING AGILE WORKFLOW Agileemancipates TEAMS… Emphasis oncoordinationandcommunication. Tighterlocalizationanddevelopmentintegration. More transparency.

6. TESTING AGILE WORKFLOW TEAM COMMUNICATION • Continuous communication • Implement centralized tools • Clarify workflows • Sync and review materials Indeterminationleads to poorefficiency ENSURE YOUR TEAM KNOWS WHAT TO DO

7. PART II AgileQA Planning & Workflow

8. TESTING AGILE WORKFLOW Localizationvision • Pre-analysis for new project • Establish string typology • Draft GUI mockups with development teams • Draft style guide (capitalization, register, hyphenation, glossary, punctuation)

9. TESTING AGILE WORKFLOW Localization PRE-PLANNING • Establish localization environment • Sync with code repositories • Request tracking • Identify actors and integrate LSPs in workflow • Resource planning and necessary outsourcings • Release plan settlement (simshipor gradual?) Localizationisnot a service “black box” GLASS-BOX PRINCIPLE

10. TESTING AGILE WORKFLOW AGILE WORKFLOW • Integrate outsourcedresources(centralizedin-house TMS, Wiki, repositoriesaccess) • Invest in languageneutralityandlong-termframeworks • Rapiddeploymentpreparation

11. TESTING AGILE WORKFLOW LOCALIZATION SCOPE • Establishpriorization • Assesslocalizableresources: strings, images, GUI adaptation • Planlocalizationstages

12. TESTING AGILE WORKFLOW TEST STRATEGY • Testingpractices • Storytesting • Testautomation • Testingtoolsandenvironment • Requirements for testing • Syncedwithwidercompanyobjectives andpractices MULTI-PROJECT, LONG-TERM GOALS

13. TESTING AGILE WORKFLOW TEST PLANNING • Solutionverificationtesting • Useracceptancetesting • Priorize andsystematize: ExploratorytestingUsabilitytestingFunctionalitytesting • Drafttest cases • Syncwithdevelopment PROJECT AND REQUIREMENT-SPECIFIC

14. TESTING AGILE WORKFLOW INTEGRATION TESTING MODEL GLOBALIZATION TESTING LOCALIZABILITY TESTING LOCALIZATION TESTING Project Start Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6 Project End

15. TESTING AGILE WORKFLOW INTEGRATION TESTING MODEL ComplementaryLocalization/DevelopmentCycles Best for centralizedandtightteams. Software developmentandlocalization processes are complementary. Translationiscarriedoutwithintheuser-storyscope. LOCALIZATION DEVELOPMENT

16. TESTING AGILE WORKFLOW INTEGRATION TESTING MODEL ComplementaryLocalization/DevelopmentCycles • QA is a combinationof AUTOMATED and MANUAL testing. • AUTOMATED • Regressiontests • New functionaltest cases • MANUAL • Linguistic LOcALIZATION DEVELOPMENT

17. TESTING AGILE WORKFLOW Localizationprocess

18. PART III AgileTesting QA

19. TESTING AGILE WORKFLOW TestingMETHODologieS • Integratedtestanddevelopmentenvironments • Combinationoftestingmethods • Resourceandproject-dependent • Accuratetest case management

20. TESTING AGILE WORKFLOW TestingMETHODologieS 3 1 2 MANUAL AUTOMATED SEMI-AUTOMATED Advantages: Languageconsistency Style/registerissues Terminologyissues Feedback onin-contextusabilitytesting

21. TESTING AGILE WORKFLOW TestingMETHODologieS 3 1 2 MANUAL AUTOMATED SEMI-AUTOMATED Disadvantages: Training curve required Highriskofinconsistencies Time-consuming Harderlogisticalmanagement

22. TESTING AGILE WORKFLOW TestingMETHODologieS 3 1 2 MANUAL AUTOMATED SEMI-AUTOMATED Human factor withtoolsupport Test case automatization Suitable for textchecks Excellentin GUI testing

23. TESTING AGILE WORKFLOW TestingMETHODologieS 3 1 2 MANUAL AUTOMATED SEMI-AUTOMATED Functional tests Unit tests GUI validation Reusability GUI prototype validation

24. TESTING AGILE WORKFLOW Localization testing 1 LINGUISTIC Capitalization Cultural adequacy Spellchecking Style/register Terminology

25. TESTING AGILE WORKFLOW Localization testing 1 2 LINGUISTIC FUNCTIONALITY Capitalization Installation Cultural adequacy Menus andhotkeys Spellchecking Replicabilityinalllanguages Style/register Input correctness Terminology Compatibility

26. TESTING AGILE WORKFLOW Localization testing 3 1 2 LINGUISTIC COSMETIC FUNCTIONALITY Capitalization Installation Truncation Content Cultural adequacy Menus andhotkeys GUI integration Spellchecking Replicabilityinalllanguages Consistency Style/register Input correctness Layout Terminology Compatibility

27. TESTING AGILE WORKFLOW AUTOMATED TESTING • Test cases replicability • GUI validation: • Alignment, truncation • Overlapping • Text: • Rendering • Blacklists, hotkeys • Linguisticchecks

28. TESTING AGILE WORKFLOW LOCALIZATION UNIT TESTS Ideal intest-drivendevelopment Automationoncodelevel Limitregressions Identify bugs sooner Reducetestingeffort @implementationtests -(void)testCreateFoo { STAssertNotNil (foo, @”Unable to createdialog”); } ... • Checksemanticson: • New build • New compilation

29. TESTING AGILE WORKFLOW LOCALIZATION TEST STAGES Localizationrequirements Technicalframework Productinternationalization Cultural appropriateness Renderingengine GUI changes Frameworks Test cases ACCEPTANCE INTEGRATION TEST CYCLE Codesemanticscheck Strings ID andcontent Locale files dependencies Time zone/cultural marks GUI layout(mobile and desktop apps) Bug fixing Textrefactoring Updatediconsandgraphics Codeupdates REGRESSION UNIT TESTS

30. CONCLUSIONS • Workcloselywithandatanearlystage • Keepexpectationsrealistic • Trainskill-based role sharing • Engagestakeholders as theywillinfluencethecompanyculture • Makelocalization QA an integral partoftheprojectplan

31. QUESTIONS? DOUBTS? THANK YOU FOR YOUR ATTENTION ALBERTO FERREIRA alberto.ferreira@avira.com AviraOperationsGmbH & Co. KG