How To Become A Good Agile Tester?
Download as PPTX, PDF1 like287 views
This document discusses how to be a good agile tester. It outlines the agile testing approach which focuses on quality assistance over assurance, continuous testing over end testing, team responsibility over individual responsibility, and automated assessment over regression testing. It also discusses the advantages of agile such as customer satisfaction through continuous delivery, less communication gaps, and attention to detail. Finally, it lists the qualities of a pro agile tester including pre-iteration verification, short feedback loops, being always active and alert, using CI/CD, executing automation, performing parallel independent testing, and conducting lifecycle testing.
How To Become A Good Agile Tester?
- 1. HOW TO Be A Good Agile Tester?
- 2. What is Agile Model? ■ A group of Software Development Methodologies ■ Promotes continuous iteration in a SDLC ■ Incremental and iterative testing and development ■ Adds value to the product release as well as production
- 3. AgileTestingApproach ■ QualityAssistance over QualityAssurance ■ ContinuousTesting over testing it at the end ■ Team Responsibility over tester’s or developer’s responsibility ■ Automated Assessment over RegressionTesting ■ Short Feedback Loop over Delayed Feedback ■ Preventing Defects over Detecting Defects
- 4. Advantages of Agile ■ Customer satisfaction ---Continuous Delivery ■ Less communication gap due to maximum team interaction ■ Close discussions between stakeholders and team (testers, developers, etc.) ■ Attention to detail --- QA ■ Flexible towards money and minute constraints
- 5. Tester’s Role in AgileTesting ■ Performs iterative testing ■ Analyses business requirements and expectations ■ Cross-sectional and interactive testing with developers ■ InfluencesTesters to include testability in their coding practices ■ The collaboration help them predicting future improvements
- 6. Qualities of a Pro AgileTester ■ Pre-Iteration Early verification of requirements to ensure quality later ■ Short Feedback Loop Finds a bug and reports it to the developer quickly ■ Always Active & Alert Influential, innovative, estimates, and suggests better enhancements for QA ■ CI/CD Runs test cycles on the addition of every new build and entity and reports a bug if necessary ■ Executes Automation Responds with previously built automated scripts to cope with any change ■ Parallel IndependentTesting Takes ownership of the most difficult trusting parts of the SDLC apart from its team ■ LifecycleTesting Validation of the product at the end of software development lifecycle to assure secure production.