Agile testing - Reducing time to Market

3,555 views

Published on

Agile Testing - strategies to reduce time to market

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

No Downloads
Views
Total views
3,555
On SlideShare
0
From Embeds
0
Number of Embeds
2,203
Actions
Shares
0
Downloads
26
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide
  • Traditional testing focus on conformance to requirements
  • Change in market trends
    Shorter product cycle
  • Agile testing - Reducing time to Market

    1. 1. Agile Testing- Reducing the time to market Manoj K G Founder and Director, TeamSuccesso
    2. 2. Reference
    3. 3. Agile Software Methodologies SCRUM KANBAN
    4. 4. Who is an Agile Tester?
    5. 5. Delivery Side Business Side Agile Tester Agile Team FOCUS ON QUALITY CUSTOMER NEEDS
    6. 6. How does the Agile Tester contribute?
    7. 7. Testing in Agile is a whole team responsibility
    8. 8. What’s different in Agile? 4 4 1 2 5 6 2 3 5 1 1 7 2 3 3 1 Focus on Incremental Delivery
    9. 9. How often do you release?
    10. 10. 1 time in every two year to 50 times a day
    11. 11. Existing features
    12. 12. OK, back to some fundamentals…..
    13. 13. Iterative Model- When are you identifying the bugs? Req. capture New feature 1X Cost to Fix 5X New feature Regression-existing function 10X Regression-existing function Beta testing 100X Beta testing
    14. 14. From Agile Testing by Lisa and Janet
    15. 15. From Agile Testing by Lisa and Janet
    16. 16. Unit Tests – Leveraging TDD
    17. 17. Unit Tests 1. Written by programmers 2. Part of Definition of Done 3. Reviewed with testers TDD is a SKILL which requires investment from management and team
    18. 18. Upper Environment Code quality Unit Test coverage Functional Test coverage Lower Environment Guard your gates during code deployments
    19. 19. Blue Green Deployments
    20. 20. BUG Driven Unit tests Simulate identified bug by a automated test Write code to make the unit test pass Refactor the covered code
    21. 21. From Agile Testing by Lisa and Janet
    22. 22. Role of Quadrant 2 tests
    23. 23. Guides development by programmers
    24. 24. Providing early feedbacks
    25. 25. Functional tests 1. 2. 3. 4. Written by testers Inputs for developers Part of Definition of Done Consulted with developers Automation of functional tests are critical for early feedbacks
    26. 26. From Agile Testing by Lisa and Janet
    27. 27. Role of Quadrant 3 tests
    28. 28. 80% of repetitive testing efforts comes from scenarios in Q1 and Q2 In Q3, Unleash the power of human intellect for increasing the value of the product
    29. 29. Scenario testing, Exploratory testing, Usability Testing
    30. 30. Soap Opera Testing
    31. 31. Use Personas
    32. 32. From Agile Testing by Lisa and Janet
    33. 33. Focus on the nonfunctional requirements that increase the value of Product
    34. 34. Functional tests 1. Done by testers/programmers/ Specialists 2. Should be part of user stories
    35. 35. Transforming a Legacy application to Agile Testing
    36. 36. Refactor your tests
    37. 37. Risk Based Testing
    38. 38. Automate from RBT
    39. 39. Thank you twitter - https://twitter.com/goodoldmanoj Blog - www.techbudha.com LinkedIn - http://www.linkedin.com/pub/manoj-k-g/12/811/495

    ×