Agile Testing - Approach and Strategies
Download as PPTX, PDF0 likes126 views
Agile testing is a practice aligned with agile software development principles, enabling testing to start early and continue throughout the development process. It offers advantages such as time and cost savings, less documentation, and frequent user feedback, yet it also poses challenges like increased errors due to reduced documentation and the need for testers to adopt developer roles. Effective communication among teams is crucial for successful agile testing, which necessitates thorough and frequent regression testing to ensure product quality.
Agile Testing - Approach and Strategies
- 1. Agile Testing Afaq Mansoor Khan | Nouman Khan Teacher: Mr. Ahsan Ashfaq Subject: Software Verification & Validation
- 2. What is Agile Testing? AGILE TESTING is a testing practice that follows the rules and principles of agile software development. Unlike the Waterfall method, Agile Testing can begin at the start of the project with continuous integration between development and testing. Agile Testing is not sequential but continuous.
- 3. Agile Testing Strategies Agile testing life cycle spans through four stages
- 4. The Agile Testing Quadrants
- 5. Advantages of Agile Testing ● Agile Testing Saves Time and Money ● Less Documentation ● Regular feedback from the end user ● Daily meetings can help to determine the issues well in advance
- 6. Quality Assurance challenges with Agile software development 1) Chances of error are more in agile, as documentation is given less priority, eventually puts more pressure on QA team. 2) Testers are often required to play a semi-developer role. 3) Very less time to prepare test plan. 4) For regression testing, they will have minimal timing. 5) Requirement changes and updates are inherent in an agile method, becoming the biggest challenge for QA.
- 7. Risk of Automation in Agile Process 1) Automated UI provides a high level of confidence, but they are slow to execute, fragile to maintain and expensive to build. 2) Automated tests are not a replacement for an exploratory manual testing. To obtain the expected quality of the product, a mixture of testing types and levels is required. 3) In order to save time, much times the automation test plan is poorly planned or unplanned which results in the test fail. 4) Productivity metrics such as a number of test cases created or executed per day can be terribly misleading.
- 8. Conclusion Agile testing involves testing as early as possible in the software development lifecycle. It demands high customer involvement and testing code as soon as it becomes available. The code should be stable enough to take it to system testing. Extensive regression testing can be done to make sure that the bugs are fixed and tested. Mainly, Communication between the teams makes agile testing a success!!!
- 9. References 1) https://www.guru99.com/agile-testing-a-beginner-s-guide.html 2) https://reqtest.com/testing-blog/agile-testing-principles-methods-advantages/ 3) https://www.tutorialspoint.com/software_testing_dictionary/agile_testing.htm