Overview
Traditional risk-based test practice is challenged by incremental delivery. This two-day course examines concepts such as pair testing, strengthening relationships, working in sync with the developers and incremental confirmed component delivery. The course points out the differences between traditional testing and Agile testing methods, highlighting the changes that need to be made to apply the best testing principles. The course introduces participants to the Agile testing process, and explores the practices that will be of immense help to the participants in their work life.
What You'll Learn
- Improve software quality delivered by the Agile development teams
- Apply all four quadrants of software testing to ensure the effectiveness of both business facing and technology facing testing
- Accelerate defect detection and correction, and lower integration costs through continuous integration
- ‘Build the product right’ by applying techniques like Test-Driven Development (TDD)
- Capitalize on your investment in traditional testing methods by transitioning them to an Agile approach
- Address product and technical risk using Risk-based testing to better focus the time and the resources
- Enhance the skills of your testers and development team to effectively conduct adequate testing
- Learn from defects so you can optimize your Agile development process
- Achieve higher product confidence by using Pair Testing
- Optimize the performance of your Agile teams through proper testing roles
Curriculum
- Origins of Agile testing
- Agile testing vs. Traditional approaches
- Agile testing principles
- Whole team approach
- Building quality
- Continuous improvement and feedback
- Exercise: Ingraining the Agile Testing Mindset
- Agile testing: Quadrants of the categories
- Automation pyramid: introduction
- Testing techniques
- Unit and component testing
- Pairing between Developer and Tester
- Acceptance Test-Driven Development (ATDD)
- Behavior-Driven Development (BDD)
- Spec by Example
- User story testing
- Feature testing
- Exploratory testing
- Non-functional testing
- Team-based testing approach
- Typical business representative role in testing
- Typical programmer role in testing
- Typical tester role in testing
- Role of test managers in Agile
- Different strategies based on levels of precision
- During iteration planning and kickoff
- Lightweight test plan documentation
- Defect tracking and management
- Result reporting
- Test metrics
- Regression tests
- Time-boxed delivery
- Continuous delivery
- Post-development test cycles
- Iteration wrap-up
- Definition of a release/end game
- User Acceptance Test (UAT)
- System-wide and cross-team testing
- Post-release testing
- Documentation for regulatory requirements
- Typical environments for Test
- Build pipeline
- Automated builds
- Testing the proper build
- Test data management
- Distributed Team Communication
- Distributed Team Coordination
Who should attend
- Quality analysts and engineers
- Software test leads and testers
- Software quality and testing managers
- Software project managers
- Software engineering managers
- Business analysts
- Software development managers
- IT managers
- Programmers/developers