What is Agile Testing
•Télécharger en tant que PPTX, PDF•
0 j'aime•1,107 vues
Introduction to Agile Testing
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (19)
En vedette
Similaire à What is Agile Testing
Similaire à What is Agile Testing (20)
Plus de ShriKant Vashishtha
Plus de ShriKant Vashishtha (12)
Dernier
Dernier (20)
What is Agile Testing
- 1. What is Agile Testing? By ShriKant Vashishtha
- 4. Agile – One Team, One Mission
- 5. Time Analysis Design Coding Testing 20% done (100% usable!) Time Analysis Design Coding Testing 20% done (usable = not yet) Traditional Process Agile Process Agile = Early Value
- 6. ALL THIS IS ACHIEVED THROUGH…
- 9. ROLE OF A TESTER IN AGILE PROJECT
- 10. Typical Cardwall in Agile Project
- 11. Proactive Team Member – Avoid Bugs to Happen
- 12. Dev Box Testing
- 14. Help PO in Achieving “Definition of Ready”
- 15. Typical Cardwall in Agile Project
- 16. Gateway to “Definition of Done”
- 17. QUALITY FOCUS IN AGILE
- 18. Continuous Integration and Quality Build
- 19. Focus on Automated Testing
- 20. UNIT AND INTEGRATION TESTING
- 21. TDD and Unit Testing
- 22. TDD Cycle
- 24. Options • Selenium • QTP • Sahi • FitNesse
- 25. ATDD
- 26. What’s in the Name • Acceptance Test-Driven Development • Behavior-Driven Development (BDD) • Specification by Example • Agile Acceptance Testing • Story Testing
- 27. BDD
- 28. ATDD in Distributed Agile
- 29. Scrip less Testing Automation • QTP • Tosca
- 30. POTENTIAL ISSUES FOR TESTERS IN AGILE TEAMS
- 31. Estimation not Done as a Team
- 32. Not Enough Time for Testing
- 33. Silos in Agile Teams
- 34. Questions
Notes de l'éditeur
- WelcomeDisclaimer:Series of webinars on Agile TestingFirst one is focused on the foundation and building blocks of the Agile Testing which in my view is very very important to understand.This session will not cover detailed technical aspects of test automation.Questions:Questions will be answered at the end of the session. Please use chat window to enter your questions and responses.
- How is it different to work in Agile environment to work as a tester.Is it just the mindset change and or it impacts the way we work also?
- SilosBiggest goal looks like our individual profession – i.e. development, testing, business analysis or deployment.Similarly customer is also in defensive or offensive mode – fear of change requests and he would like to dump everything in the requirements document he could think of.Result – it looks like nobody really focus on why they are working at the first place – to build a product which delights the end user, delivered when it could be used.In this case – tester’s focus is to find bugs in the code. Depending on number of bugs he find, the greatness of tester increases.
- Everybody works towards a team goal. Which is to create a great product or application.As part of two weeks if development is done but testing is not completed – nothing could be shown to the customer – translates into zero business value.DB design is done but UI not done – it’s not done.As the focus is towards a team goal, in order to achieve that, everybody has to work as one team, collaborate and support each other.How this support and collaboration happens in agile will be discussed in next slides.
- In first picture – 20% done means nothing is usable yet.In Agile – 20% done means – 100% usable.How is it possible to deliver value in 2 weeks in Agile compared to 6 months of waterfall cycle?
- Collaboration to achieve the team goalAnd being cross functionalTraditional – one person knows one part of functionality and only he can work on it.Agile – due to pair programming everybody can potentially work on everything
- There is continuous discipline and focus on quality.There are more technical practices involved in order to achieve production level quality as part of 2 weeks cycle.The best way to speed up and having less errors is to automate the quality part.Will be discussed in the later part of the presentation.