Beruflich Dokumente
Kultur Dokumente
Deterministic Outcome
* How do I determine success/failure
Remember!
of test ?
– Common Types of
Tests
– MenuWalker
– Functional
- Scenario
- Random
- Automated
- Interoperability
- Language Quality
- Data Path
- Boundary
Incremental Testing Strategy
- I18N
For optimal efficiency, your L10N teams should not
test baseline functionality! It should focus on
incrementally testing that the product integrity is
maintained through the localization process.
QA Engineering Types of
Testing
– Functional
Automator, beware ! • Verify product functional
integrity using automated
- Scenario test cases
- Random
Automation is Resource Intensive Execution
Automated
- •Developing Automated Scripts can be time-consuming
• Structured testing of
application in controlled
Need understanding of programming techniques
- •System scenarios
• If not developed correctly, can be very high on maintainence
- Acceptance • Very effective with
No Replacement for real testing
- Language Quality comparative test cases
• Can compliment but not replace real ‘testers’ Outcomes
- Data Path Deterministic
Not everything adapts well to test automation
- Boundary • Software integrity is
• Good : Tests that verify an applicationmaintained
works in a in controlled
particular test
way
- I18N cases
• Bad : Tests that find previously undiscovered errors
- Performance • Acceptance of software at
significant project
milestones
QA Engineering Types of
Testing
– Functional
Factors to Consider during Performance •Determine how system
Testing
operates under ‘Load’
- Scenario
Network Capacity conditions
- •Random
Concurrent users Execution
- •Automated
Remote Sessions/Connections • Structured environments
used to test application
- System
Disk, Memory and CPU Usage
• Relatively easy to
- •Acceptance
Run system under minimum and maximum boundary conditions
automate
- Language
Transaction LoadingQuality Deterministic Outcomes
- •Data Path
Continuous transaction loading over time
• Application operates
- Boundary successfully under stressful
load conditions
- I18N • May identify areas of
- Performance functionality for
optimization by Development
team
QA Engineering Managing &
Tracking
– Tracking your QA
Engineering Projects
– Coverage Reports
– By Platforms
– By Module,
Component, Unit
– By Tester
– By Build, Release
– By Language
– Bug Tracking
– 3 Point Tracking
450
400
– By Category,
350
300
Open
Severity
250
Closed
200
Pending
150
– Pending Tracking
-
1 2 3 4 5 6 7 8
– Language Quality
Reports
– Terminology
Consistency Report
– Sampling Reports
– Error Density
QA Engineering Tools to Help
you Manage
IQA Cycle
Disadvantages
–Localization & IQA not integral to base development
–Base Product completes before any focus on International Issues
–IQA bugs only addressed after release of base product
–No sharing and coupling of test plans between Base QA and IQA teams
–No International Product Development Planning
IQA Cycle
Advantages
–IQA is an integral part of the PD Lifecycle
–Releasing localized products is a Corporate Wide Goal
–Base QA team are aware of and implementing IQA in their Base Product QA
plans
–Development fix IQA issues as they develop Base product
–Corporate Goal : Universal English Product
let Result = x * y / z
return Result
}