This document discusses agile testing and how it can help reduce time to market. It covers agile methodologies like Scrum and Kanban. An agile tester works with the agile team to focus on quality and customer needs. Testing in agile is a shared responsibility. The document discusses iterative testing, unit testing using test-driven development, functional testing, and non-functional testing. It also covers risk-based testing and transforming legacy applications to agile.

1. Agile Testing- Reducing the time
to market
Manoj K G
Founder and Director, TeamSuccesso

2. Reference

3. Agile Software Methodologies
SCRUM
KANBAN

4. Who is an Agile Tester?

5. Delivery Side
Business Side
Agile Tester
Agile Team
FOCUS ON QUALITY CUSTOMER NEEDS

6. How does the Agile Tester contribute?

7. Testing in Agile is a whole team
responsibility

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. How often do you release?

10. 1 time in every two year to 50 times a day

11. Existing features

12. OK, back to some fundamentals…..

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. From Agile Testing by Lisa and Janet

15. From Agile Testing by Lisa and Janet

16. Unit Tests – Leveraging TDD

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. Upper Environment
Code quality
Unit Test coverage
Functional Test coverage
Lower Environment
Guard your gates during code deployments

19. Blue Green Deployments

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. From Agile Testing by Lisa and Janet

22. Role of Quadrant 2 tests

23. Guides development by programmers

24. Providing early feedbacks

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. From Agile Testing by Lisa and Janet

27. Role of Quadrant 3 tests

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. Scenario testing,
Exploratory testing,
Usability Testing

30. Soap Opera Testing

31. Use Personas

32. From Agile Testing by Lisa and Janet

33. Focus on the nonfunctional requirements
that increase the value of Product

34. Functional tests
1. Done by testers/programmers/
Specialists
2. Should be part of user stories

35. Transforming a Legacy
application to Agile Testing

36. Refactor your tests

37. Risk Based Testing

38. Automate from RBT

39. Thank you
twitter - https://twitter.com/goodoldmanoj
Blog - www.techbudha.com
LinkedIn - http://www.linkedin.com/pub/manoj-k-g/12/811/495