This document discusses test automation in agile projects. It begins with an overview of agile principles like the agile manifesto. It then discusses agile testing principles and practices like continuous integration and continuous delivery. The bulk of the document focuses on test automation, including why it's important, different types of test automation frameworks, and design considerations like the test automation pyramid. It provides tips for test automation including design patterns, abstraction layers, and evolving the framework over time.

1. TEST AUTOMATION IN
AGILE PROJECTS
“WHAT? WHY? HOW?”
Anand Bagmar
Test Practice Lead

2. @BagmarAnand
about.me/anand.bagmar
ABOUT ME

3. What Is Agile?

4. Source: http://dilbert.com/strip/2007-11-26
Reference: http://martinfowler.com/articles/agileFluency.html

5. Agile Manifesto

6. Source: http://agilemanifesto.org/
AGILE MANIFESTO
Individuals
and
Interactions
Processes
&Tools
over

7. Source: http://agilemanifesto.org/
AGILE MANIFESTO
Working
Software
Comprehensive
Documentation
over

8. Source: http://agilemanifesto.org/
AGILE MANIFESTO
Customer
Collaboration
Contract
Negotiation
over

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

10. Agile Testing
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. Principles & Practices
of
Agile Testing

16. OUR PRIMARY OBJECTIVE
Faster Delivery Of Quality Software From
Idea To Consumer

17. Building Quality In
Involving Everyone
Fast Feedback
Tests Are An Asset
Faster Delivery Into Production
Clear View Of Testing
Business Optimize Value
TESTING PRINCIPLES

18. Continuous
Integration (CI)

19. CONTINUOUS INTEGRATION (CI)
”… is a software development practice where members of a team
integrate their work frequently, usually each person integrates at
least daily - leading to multiple integrations per day. Each
integration is verified by an automated build (including test)
to detect integration errors as quickly as possible…."
- Martin Fowler, ThoughtWorks Chief Scientist
Ø http://www.thoughtworks.com/continuous-integration

20. CI PROCESS

21. Continuous
Delivery (CD)

22. CONTINUOUS DELIVERY (CD)
… is the natural extension of Continuous Integration: 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
button. Continuous Delivery aims to make releases boring, so
we can deliver frequently and get fast feedback on what users
care about.
- Martin Fowler, ThoughtWorks Chief Scientist
Ø http://www.thoughtworks.com/continuous-delivery

23. CONTINUOUS DELIVERY

24. Practices, Tips & Tricks
QA

25. Test Automation
A PRACTICE THAT MAKES TEAMS SUCCESSFUL?

26. Test Automation
A PRACTICE THAT MAKES TEAMS UNSUCCESSFUL?

27. What is
Test Automation?

28. Automation
-
A Safety Net

29. Why do we do
Test Automation?

30. QUICK FEEDBACK

31. How to get quick
feedback from
Test Automation?

32. • “Succeeding with Agile” – Mike Cohn
• Martin Fowler – Test Pyramid
martinfowler.com/bliki/TestPyramid.html
THE TEST PYRAMID

33. IDEAL TEST AUTOMATION PYRAMID
Unit
Manual / Exploratory
Integration
JavaScript
View
Web Service
UI
Cost
Impact
Time
Business-
facing
Tests
Technology-
facing
Tests

34. REALITY

35. ICE-CREAM CONE ANTI PATTERN
Manual / Exploratory
UI
Web Service
View
JavaScript
Integration
Unit

36. Web Service
View
JavaScript
Integration
Unit
Developers Test Pyramid QA Team Test Pyramid
DUAL TEST PYRAMID ANTI-PATTERN
Manual / Exploratory
UI
Web Service

37. CUP-CAKE ANTI-PATTERN

38. TYPES OF TEST AUTOMATION FRAMEWORKS
Modular
Data-driven
Keyword-driven
Model-based
Hybrid
? ? ?

39. Understand
the
system(s)
/
product(s)
you
need
to
test!!
REMEMBER …

40. TEST AUTOMATION FRAMEWORK DESIGN CRITERIA
Maintainable
Scalable
Browser / Device support
Support features of
Product-under-test
Easy to Use
Different
Environments
Parallel Execution
Tool support
Reports & Metrics
Support the types
of testing required
Operating System &
Database support
Run locally & remotely
Language / tool
restrictions

41. PRINCIPLES FOR TEST AUTOMATION FRAMEWORK
Design Patterns
Abstraction Layers
Headless executing
Evolve
Code Quality
Take Screenshots
Refactor
Tools & Utilities
Extensible
Run via CI
Logging
Video Recording
Test Data

42. FRAMEWORK ABSTRACTION LAYERS

43. Patterns for building
a Test Automation
Framework

44. Page Object Pattern
Business-Layer Page
Object Pattern

45. Business Layer Page
Object Pattern

46. FRAMEWORK ABSTRACTION LAYERS

47. Evolve as you Learn

48. Source: http://dilbert.com/strip/2005-11-16

49. abagmar@gmail.com
Anand.Bagmar@thoughtworks.com
@BagmarAnand
about.me/anand.bagmar
THANK YOU