Agile Methodology is not new. Many organisations / teams have already adopted Agile way of Software Development or are in the enablement journey for the same. What does this mean for Testing? There is no doubt that the Testing approach and mindset also needs to change to be in tune with the Agile Development methodology. Learn what does it mean to Test on Agile Projects.

1. WHAT IS AGILE
TESTING?
Prasad Kalgutkar
&
Amit Gundiyal

2. Money /
Value
Time
Quality
ORGANIZATION OBJECTIVE

3. What Is Agile?

4. Source: h*p://rlacovara.blogspot.in/2009/09/angry-coders-many-faces-of-agile.html

5. Agile Manifesto

6. AGILE MANIFESTO
Individuals
and
Interactions
Processes
and
Tools
Source: h*p://agilemanifesto.org/
over

7. AGILE MANIFESTO
Working
Software
Comprehensive
Documentation
Source: h*p://agilemanifesto.org/
over

8. AGILE MANIFESTO
Customer
Collaboration
Contract
Negotiation
Source: h*p://agilemanifesto.org/
over

9. AGILE MANIFESTO
Responding
To
Change
Following
A Plan
Source: h*p://agilemanifesto.org/
over

10. Agile Tes=ng
Manifesto

11. AGILE TESTING MANIFESTO
Collaborative
Ownership
Detached
Objectivity
over

12. AGILE TESTING MANIFESTO
Targeted
Automation
Widespread
Anti-regression
over

13. AGILE TESTING MANIFESTO
Defect
Prevention
Defect
Detection
over

14. AGILE TESTING MANIFESTO
Exploratory
Testing
Predetermined
Scripting
over

15. AGILE TESTING MANIFESTO
Value
Addition
Persistent
Critic
over

16. Are We Building the Correct Product &
….
If so, are we building it correctly?

17. Principles & Prac=ces of
Agile Tes=ng

18. PRINCIPLE: INVOLVE EVERYONE
Tes=ng ≠ Testers
Quality is a Team Responsibility

19. PRINCIPLE: BUILD QUALITY IN
Preven+ng
Defects
Finding
Defects
Preven+ng
Defects
Finding
Defects

20. QA - BA
QA - Dev
QA - UX
QA – DevOps
QA - Stakeholder
PRINCIPLE: BUILD QUALITY IN

21. PRINCIPLE: FAST FEEDBACK
QUICK
RESPONSE

22. PRINCIPLE – BUSINESS OPTIMIZE VALUE
PEOPLE
TECHNOLOGYPROCESS
Quality is not just in the soRware but also in the process

23. Typical Ac=vi=es in
Agile Teams

24. STORY PLANNING SESSION
Story Planning Session
Write Story & Scenarios
BA
Implement Automated
Acceptance Tests
TESTER
DEV TESTER
Implement Functionality
Regular BA/QA Demo
DEV DEV
TESTERDEV BA
Showcase to
Business
START DEVELOPMENT ITERATION
DEVELOPMENT
ENGINE
BUSINESS BA
TESTER
Story Testing
BA / QA Signoff on Dev Box
BADEV TESTER
TESTER
BABUSINESS
Starts Here
System Testing
END DEVELOPMENT
ITERATION

25. STORY WRITING
BA
Story Planning Session
Write Story & Scenarios
BA
Implement Automated
Acceptance Tests
TESTER
DEV TESTER
Implement Functionality
Regular BA/QA Demo
DEV DEV
TESTERDEV BA
Showcase to
Business
START DEVELOPMENT ITERATION
DEVELOPMENT
ENGINE
BUSINESS BA
TESTER
Story Testing
BADEV TESTER
TESTER
BA / QA Signoff on Dev Box
BABUSINESS
Starts Here
System Testing
END DEVELOPMENT
ITERATION

26. AUTOMATE ACCEPTANCE TESTS
BA
Story Planning Session
BUSINESS
Write Story & Scenarios
BA
Implement Automated
Acceptance Tests
TESTER
DEV TESTER
Implement Functionality
Regular BA/QA Demo
DEV DEV
TESTERDEV BA
Showcase to
Business
START DEVELOPMENT ITERATION
DEVELOPMENT
ENGINE
BUSINESS BA
TESTER
Story Testing
BADEV TESTER
TESTER
BA / QA Signoff on Dev Box
BA
Starts Here
System Testing
END DEVELOPMENT
ITERATION

27. IMPLEMENT FUNCTIONALITY
BA
Story Planning Session
BUSINESS
Write Story & Scenarios
BA TESTER
DEV TESTER
Implement Functionality
Regular BA/QA Demo
DEV DEV
TESTERDEV BA
Showcase to
Business
START DEVELOPMENT ITERATION
DEVELOPMENT
ENGINE
BUSINESS BA
TESTER
Story Testing
BADEV TESTER
TESTER
BA / QA Signoff on Dev Box
Implement Automated
Acceptance Tests
BA
Starts Here
System Testing
END DEVELOPMENT
ITERATION

28. BA & QA SIGNOFF
BA
Story Planning Session
BUSINESS
Write Story & Scenarios
BA TESTER
DEV TESTER
Implement Functionality
Regular BA/QA Demo
DEV DEV
TESTERDEV BA
Showcase to
Business
START DEVELOPMENT ITERATION
DEVELOPMENT
ENGINE
BUSINESS BA
TESTER
Story Testing
BADEV TESTER
TESTER
BA / QA Signoff on Dev Box
Implement Automated
Acceptance Tests
BA
Starts Here
System Testing
END DEVELOPMENT
ITERATION

29. STORY TESTING
BA
Story Planning Session
BUSINESS
Write Story & Scenarios
BA TESTER
DEV TESTER
Implement Functionality
Regular BA/QA Demo
DEV DEV
TESTERDEV BA
Showcase to
Business
START DEVELOPMENT ITERATION
DEVELOPMENT
ENGINE
BUSINESS BA
TESTER
Story Testing
BADEV TESTER
TESTER
BA / QA Signoff on Dev Box
Implement Automated
Acceptance Tests
BA
Starts Here
System Testing
END DEVELOPMENT
ITERATION

30. SHOWCASE TO BUSINESS
BA
Story Planning Session
BUSINESS
Write Story & Scenarios
BA TESTER
DEV TESTER
Implement Functionality
Regular BA/QA Demo
DEV DEV
TESTERDEV BA
Showcase to
Business
START DEVELOPMENT ITERATION
DEVELOPMENT
ENGINE
BUSINESS BA
TESTER
Story Testing
BADEV TESTER
TESTER
BA / QA Signoff on Dev Box
Implement Automated
Acceptance Tests
BA
Starts Here
System Testing
END DEVELOPMENT
ITERATION

31. What else will make
us successful?

32. Automa=on
(A Safety Net)

33. And what can make
us unsuccessful?

34. Automa=on
(A Entangled Net)

35. HOW?

36. TEST PYRAMID
Manual / Exploratory
Impact
Business-
facing
Tests
Technology-
facing
Tests
Time
Cost
Integra=on
JavaScript
Web Service
UI
Unit
View

37. REALITY

38. ICE-CREAM CONE ANTI PATTERN
Manual / Exploratory
-----------------
UI
-----------------
Web-Service
-----------------
View
-----------------
JavaScript
-----------------
Integra=on
---------------
Unit

39. Web Service
View
JavaScript
Integra=on
Unit
Developers Test Pyramid QA Team Test Pyramid
DUAL TEST PYRAMID ANTI-PATTERN
Manual / Exploratory
UI
Web Service

40. CUP-CAKE ANTI-PATTERN

41. Con=nuous
Integra=on (CI)

42. CONTINUOUS INTEGRATION (CI)
”… is a soNware development pracPce where members of a team
integrate their work frequently, usually each person integrates at least
daily - leading to mulPple integraPons per day. Each integra=on is
verified by an automated build (including test) to detect integra=on
errors as quickly as possible…."
- MarPn Fowler, ThoughtWorks Chief ScienPst
➢➢ h*p://www.thoughtworks.com/conPnuous-integraPon

43. CI PROCESS

44. Con=nuous
Delivery (CD)

45. CONTINUOUS DELIVERY (CD)
… is the natural extension of ConPnuous IntegraPon: an approach in which
teams ensure that every change to the system is releasable, and that
we can release any version at the push of a bu*on. ConPnuous Delivery
aims to make releases boring, so
we can deliver frequently and get fast feedback on what users care
about.
- MarPn Fowler, ThoughtWorks Chief ScienPst
➢➢ h*p://www.thoughtworks.com/conPnuous-delivery

46. CONTINUOUS DELIVERY

47. Thank you
We would like to hear from you:
Prasad - prasadk@thoughtworks.com
Amit - amit.gundiyal@thoughtworks.com