An Organic Mechanism
description
Transcript of An Organic Mechanism
An Organic Mechanism
Effective Localization QA in Agile Development Environments
PART IAgile Principles in
Localization
TESTINGAGILE WORKFLOW
AGILE LOCALIZATION• Fast response to changing
requirements
• Collaborative
• Shorter deployment periods
• Better work tracking
• Better project integration
BUT miscommunication and unclarity compromise results.
TESTINGAGILE WORKFLOW
AGILE EMANCIPATES TEAMS…
Emphasis on coordination and communication.Tighter localization and development integration.
More transparency.
TESTINGAGILE WORKFLOW
AGILE EMANCIPATES TEAMS…
Indetermination leads to poor efficiencyENSURE YOUR TEAM KNOWS WHAT TO DO
TESTINGAGILE WORKFLOW
TEAM COMMUNICATION• Continuous communication
• Implement centralized tools
• Clarify workflows
• Sync and review materials
PART IIAgile QA
Planning & Workflow
• Pre-analysis for new project
• Establish string typology
• Draft GUI mockups with
development teams
• Draft style guide (capitalization,
register, hyphenation, glossary,
punctuation)
LOCALIZATION VISIONTESTINGAGILE WORKFLOW
Localization is not a service “black box”
GLASS-BOX PRINCIPLE
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 (simship or
gradual?)
TESTINGAGILE WORKFLOW
• Integrate outsourced resources(centralized in-house TMS, Wiki, repositories access)
• Invest in language neutrality and long-term frameworks
• Rapid deployment preparation
TESTINGAGILE WORKFLOW
AGILE WORKFLOW
Analysis
Refactoring
Review
GUI Controls
Information Messages
Log & Error Messages
• Establish priorization• Assess localizable resources:
strings, images, GUI adaptation• Plan localization stages
TESTINGAGILE WORKFLOW
LOCALIZATION SCOPE
TESTINGAGILE WORKFLOW
TEST STRATEGY• Testing practices• Story testing• Test automation• Testing tools and environment• Requirements for testing• Synced with wider company
objectives and practices
MULTI-PROJECT, LONG-TERM GOALS
TESTINGAGILE WORKFLOW
TEST PLANNING• Solution verification testing• User acceptance testing• Priorize and systematize:
Exploratory testingUsability testingFunctionality testing
• Draft test cases• Sync with development
PROJECT AND REQUIREMENT-SPECIFIC
INTEGRATION TESTING MODEL
TESTINGAGILE WORKFLOW
ProjectStart
Sprint 2
Sprint 3
Sprint 4
Sprint 5
ProjectEnd
Sprint 6
GLOBALIZATION TESTING
LOCALIZABILITY TESTING
LOCALIZATION TESTING
Draft
ImplementReview
Testing
Product incremen
t
TestingUpdate product backlog
Implement
Best for centralized and tight teams.
Software development and localization processes are complementary.
Translation is carried out within the user-story scope.
User Story Planning
Localization Draft
Localization Review
Localization Translation
Localization QA
User Story Review
TESTINGAGILE WORKFLOW
LOCALIZATION
DEVELOPMENT
INTEGRATION TESTING MODELComplementary Localization/Development Cycles
Draft
ImplementReview
Testing
Product incremen
t
TestingUpdate product backlog
Implement
QA is a combination of AUTOMATED and MANUAL testing.
AUTOMATED• Regression tests• New functional test casesMANUAL• Linguistic
User Story Planning
Localization Draft
Localization Review
Localization Translation
Localization QA
User Story Review
TESTINGAGILE WORKFLOW
LOCALIZATION
DEVELOPMENT
INTEGRATION TESTING MODELComplementary Localization/Development Cycles
Preparation
• Draft guidelines for master localization
• Mock-ups and text with Dev. & GUI teams
LocalizationProcess
• Master Localization review & testing• Pseudo-translation
Pre-Multilingual Localization
• Review & analysis• Guidelines adjustment for other
languages
TESTINGAGILE WORKFLOW
LOCALIZATION PROCESS
PART III
Agile Testing QA
TESTING METHODOLOGIESTESTINGAGILE WORKFLOW
• Integrated test and development environments
• Combination of testing methods
• Resource and project-dependent
• Accurate test case management
TESTING METHODOLOGIES1 2 3MANUAL SEMI-AUTOMATED AUTOMATED
Advantages:
Language consistency
Style/register issues
Terminology issues
Feedback on in-context usability testing
TESTINGAGILE WORKFLOW
1 2 3MANUAL SEMI-AUTOMATED AUTOMATED
Disadvantages:
Training curve requiredHigh risk of inconsistenciesTime-consuming Harder logistical management
TESTINGAGILE WORKFLOW
TESTING METHODOLOGIES
1 2 3MANUAL SEMI-AUTOMATED AUTOMATED
Human factor with tool support
TESTINGAGILE WORKFLOW
TESTING METHODOLOGIES
Test case automatization
Suitable for text checks
Excellent in GUI testing
1 2 3MANUAL SEMI-AUTOMATED AUTOMATED
TESTINGAGILE WORKFLOW
TESTING METHODOLOGIES
Functional testsUnit testsGUI validationReusabilityGUI prototype validation
LOCALIZATION TESTINGTESTINGAGILE WORKFLOW
Capitalization
Cultural adequacy
1 LINGUISTIC
Spellchecking
Style/register
Terminology
LOCALIZATION TESTINGTESTINGAGILE WORKFLOW
Capitalization
Cultural adequacy
1 2LINGUISTIC FUNCTIONALITY
Spellchecking
Style/register
Terminology
Installation
Menus and hotkeys
Replicabilityin all languages
Input correctness
Compatibility
LOCALIZATION TESTINGTESTINGAGILE WORKFLOW
Capitalization
Cultural adequacy
1 2 3LINGUISTIC FUNCTIONALITY COSMETIC
Spellchecking
Style/register
Terminology
Truncation
Content
GUI integration
Consistency
Layout
Installation
Menus and hotkeys
Replicabilityin all languages
Input correctness
Compatibility
• Test cases replicability• GUI validation:
– Alignment, truncation– Overlapping
• Text:– Rendering– Blacklists, hotkeys– Linguistic checks
TESTINGAGILE WORKFLOW
AUTOMATED TESTING Manual
TestsAutomated
GUI Tests
Automated Unit Tests
@implementation tests
-(void)testCreateFoo {STAssertNotNil (foo, @”Unable to create dialog”);
} ...
LOCALIZATION UNIT TESTSTESTINGAGILE WORKFLOW
Automation on code level
Check semantics on:• New build• New compilation
Ideal in test-driven development
Limit regressions
Identify bugs sooner
Reduce testing effort
Rendering engine
GUI changes
Frameworks
Test cases
Bug fixing
Text refactoring
Updated icons and graphics
Code updates
Code semantics check
Strings ID and content
Locale files dependencies
Time zone/cultural marks
GUI layout (mobile and desktop apps)
Localization requirements
Technical framework
Product internationalization
Cultural appropriateness
LOCALIZATION TEST STAGES
TESTCYCLE
ACCEPTANCE
UNIT TESTSREG
RESSION
INTEGRATION
TESTINGAGILE WORKFLOW
CONCLUSIONS• Work closely with and at an
early stage• Keep expectations realistic• Train skill-based role sharing• Engage stakeholders as they
will influence the company culture
• Make localization QA an integral part of the project plan
QUESTIONS? DOUBTS?
THANK YOUFOR YOURATTENTION
ALBERTO FERREIRA
[email protected] Operations GmbH & Co. KG