This document discusses enabling continuous delivery in enterprises through testing. It defines continuous integration as integrating work frequently, at least daily, and verifying with automated builds and tests. Continuous delivery aims to make releases releasable at any time through frequent, automated testing. The document recommends automating testing from the unit to user interface level. It also discusses challenges like coordinating multiple teams and environments, and emphasizes establishing the right automated testing practices, processes, and tools to achieve continuous delivery.

1. ENABLING
CONTINUOUS DELIVERY
IN ENTERPRISES WITH
TESTING
Anand Bagmar – Test Practice Lead
1

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

3. WHAT DO YOU EXPECT FROM THIS SESSION?

4. A Triangle = A Pentagon

5. CORE BANKING
IMPLEMENTATION
Case Study

6. 6

7. ORGANIZATION OBJECTIVE
Money / Value
Time
Quality

8. DISTRIBUTION / FRAGMENTATION

9. DISTRIBUTED TEAMS

10. PROGRAM SCOPE

11. PROGRAM SCOPE

12. PROGRAM SCOPE

13. PROGRAM SCOPE

14. 130 systems,
290 interfaces!
PROGRAM SCOPE

15. EXECUTION CHALLENGES
Multi-Partners
- Policies
- Constraints
- Way of working
Stakeholders
Agile
Money!
Trust

16. OTHER CHALLENGES
Co-Existence
Data Migration
Scope
Defect Management
Team Distribution
& Integration

17. NON FUNCTIONAL REQUIREMENTS
Security
Performance
Auditability
Compliance
Accessibility

18. CODE QUALITY
Core product
team(s)
Customization
team(s)
Integration &
configuration
team(s)
Systems
team(s)
NFR
Team(s)

19. How do you get early feedback in
such type of situation?

20. ORGANIZATION OBJECTIVE
Money / Value
Time
Quality

21. 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

22. CI PROCESS

23. 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

24. CONTINUOUS DELIVERY

25. HOW DO WE GET TO CONTINUOUS DELIVERY?

26. Principles & Practices

27. Test Automation
A PRACTICE THAT MAKES TEAMS SUCCESSFUL?

28. Test Automation
A PRACTICE THAT MAKES TEAMS UNSUCCESSFUL?

29. What is
Test Automation?

30. Automation
-
A Safety Net

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

32. REALITY

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

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

35. HOW DO WE GET TO CONTINUOUS DELIVERY?

36. De
Unit tests
Integration tests
Web Service tests
Functional UI Tests
Manual / Exploratory tests
Legend

37. PROGRAM SCOPE

38. De
Integrated
Environment
Developer Environment

39. De
Integrated
Environment
Developer Environment
Stubbed
Environment

40. De
Integrated
Environment
Developer Environment
Semi-Integrated
Environment
Stubbed
Environment

41. De
Integrated
Environment
Developer Environment
Semi-Integrated
Environment
Stubbed
Environment

42. De
Integrated
Environment
Developer Environment
Semi-Integrated
Environment
Stubbed
Environment
Pre-Prod
/ UAT
Environment

43. TAKEAWAYS – TO GET EARLY FEEDBACK – YOU NEED TO...
Identify tests
for specific
environments
Smart
Automation
Identify correct
& appropriate
environments
Test
Consolidation
Maintenance
Test
Prioritization
Common
repository
Categorize
Tests
Single
Dashboard
DevOps
Testing
cannot work
in isolation
Processes,
Practices & Tools

44. So ….
A Triangle == A Pentagon

45. OR …
A Triangle == A n-dimensional Polygon

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