Title: Transitioning a Team to Agile Test Methods
1Transitioning a Team to Agile Test Methods
2Outline
- Introduction
- Problems and Goals
- Test Strategy
- Weekly Automated Regression Test
- Automation Execution Architecture
- Automation Development Strategy
- Automation Design Strategy
- Automation Skills
- Conclusion
3Introduction
- Ideal scenario
- Teams Background Waterfall-based
- The whole team is globally distributed
4Problems and Goals
- The largest challenge regression testing
- Goal Replace the repetitive manual test
execution with automated tests
5Problems and Goals
6Problems and Goals
7Test Strategy
- Test Design Pairing Strategy
- User Story Test Strategy
- Regression Test Strategy
8Test Design Pairing Strategy
- Test Design Pairing Approach
- Advantage stronger correlation of testing to
the expected results - Challenge the whole team is globally distributed
9User Story Test Strategy
- On-Site Customer Product Manager
- How to write user stories simpler and modular
- Iteration Planning Meetings to make the estimates
more accurate
10Regression Test Strategy (1)
- Purpose ensure functions in previous deliveries
are not adversely affected by new code - Principle frequency of test execution and
coverage with expected feedback to developer
11Regression Test Strategy (2)
12Weekly Automated Regression Test (1)
- Provide feedback on results of the level 4
automated tests each week - Identify product regressions more efficiently by
eliminating expensive, tedious , repetitive
testing - Test multiple operating systems in parallel
- Enable testers to do more exploratory and complex
testing
13Weekly Automated Regression Test (2)
14Weekly Automated Regression Test (3)
15Automation Execution Architecture (1)
16Automation Execution Architecture (2)
17Automation Development Strategy (1)
- Past automation development was an afterthought
- Now use standard software development practices
to build change-tolerant automated test suites
18Automation Development Strategy (2)
- Build a reliable automated functional regression
suite for Level 4 regression - Use common tools and a common automation
development infrastructure - Simplify the automation development to increase
test case development velocity - Simplify the infrastructure by eliminating
redundancies - Standardize on design methods
- Simplify automation logging and results for
easier debugging and result analysis - Increase the automation development and execution
skills across the team through education sessions
19Automation Development Strategy (3)
20Automation Design Strategy
- API are used to improve reliability and
performance and in some cases reduce redundancy
in the automated scripts - Design strategy with APIs can make reworking more
affordable
21Automation Skills
- 1.Analyze Results from Automated Tests
- 2.Automation Execution via Web UI
- 3.Automation Execution via Desktop
- 4.Test Case Automation Development
- 5.Automation Framework Design
- 6.Architecture and Infrastructure Design
22Conclusion
- Key Determine the right priorities in testing
- Focusing on optimizing the test execution model
- User stories were very effective
- Have more reliability and improve performance
- 60 doing the test case development and 95 of
the team executing and debugging automation
23