What is Agile Testing

1,082 views

Published on

Introduction to Agile Testing

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,082
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
30
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • 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.
  • What is Agile Testing

    1. 1. What is Agile Testing?By ShriKant Vashishtha
    2. 2. AGILE ENVIRONMENT ANDMINDSET
    3. 3. Traditional Software DevelopmentRequirementAnalysisDeployment
    4. 4. Agile – One Team, One Mission
    5. 5. TimeAnalysisDesignCodingTesting20% done(100% usable!)TimeAnalysisDesignCodingTesting20% done(usable = not yet)Traditional Process Agile ProcessAgile = Early Value
    6. 6. ALL THIS IS ACHIEVED THROUGH…
    7. 7. Agile Culture
    8. 8. Focus on Quality
    9. 9. ROLE OF A TESTER IN AGILEPROJECT
    10. 10. Typical Cardwall in Agile Project
    11. 11. Proactive Team Member – Avoid Bugsto Happen
    12. 12. Dev Box Testing
    13. 13. Incremental Functional Testing
    14. 14. Help PO in Achieving“Definition of Ready”
    15. 15. Typical Cardwall in Agile Project
    16. 16. Gateway to“Definition of Done”
    17. 17. QUALITY FOCUS IN AGILE
    18. 18. Continuous Integration and QualityBuild
    19. 19. Focus on Automated Testing
    20. 20. UNIT AND INTEGRATION TESTING
    21. 21. TDD and Unit Testing
    22. 22. TDD Cycle
    23. 23. AUTOMATED FUNCTIONAL TESTING
    24. 24. Options• Selenium• QTP• Sahi• FitNesse
    25. 25. ATDD
    26. 26. What’s in the Name• Acceptance Test-Driven Development• Behavior-Driven Development (BDD)• Specification by Example• Agile Acceptance Testing• Story Testing
    27. 27. BDD
    28. 28. ATDD in Distributed Agile
    29. 29. Scrip less Testing Automation• QTP• Tosca
    30. 30. POTENTIAL ISSUES FOR TESTERS INAGILE TEAMS
    31. 31. Estimation not Done as a Team
    32. 32. Not Enough Time for Testing
    33. 33. Silos in Agile Teams
    34. 34. Questions

    ×