Download as PDF, PPTX
Uploaded byThoughtworks
Enabling CD in Enterprises with Testing - Anand Bagmar
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.
More Related Content
![[Webinar] Introducing Feature Management](https://cdn.slidesharecdn.com/ss_thumbnails/optimizelyfeaturemanagementdemowebinar-180516183627-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Enabling CD in Enterprises with Testing - Anand Bagmar
Enabling CD in Enterprises with Testing - Anand Bagmar
- 1. ENABLING CONTINUOUS DELIVERY IN ENTERPRISESWITH TESTING Anand Bagmar – Test Practice Lead 1
- 2.
- 3. WHAT DO YOUEXPECT FROM THIS SESSION?
- 4. A Triangle =A Pentagon
- 5.
- 6.
- 7. ORGANIZATION OBJECTIVE Money /Value Time Quality
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15. EXECUTION CHALLENGES Multi-Partners - Policies - Constraints - Way of working Stakeholders Agile Money! Trust
- 16. OTHER CHALLENGES Co-Existence Data Migration Scope DefectManagement Team Distribution & Integration
- 17.
- 18. CODE QUALITY Core product team(s) Customization team(s) Integration& configuration team(s) Systems team(s) NFR Team(s)
- 19. How do youget 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.
- 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.
- 25. HOW DO WEGET TO CONTINUOUS DELIVERY?
- 26.
- 27. Test Automation A PRACTICETHAT MAKES TEAMS SUCCESSFUL?
- 28. Test Automation A PRACTICETHAT MAKES TEAMS UNSUCCESSFUL?
- 29.
- 30.
- 31. Time Value Cost IDEAL TEST AUTOMATIONPYRAMID Manual / Exploratory UI Web Service View JavaScript Integration Unit Technology- facing Tests Business-facing Tests
- 32.
- 33. UI Web Service View JavaScript Integration Unit ICE-CREAM CONEANTI PATTERN Manual / Exploratory
- 34. Developers Test PyramidQA Team Test Pyramid Web Service View JavaScript Integration Unit Manual / Exploratory UI Web Service DUAL TEST PYRAMID ANTI-PATTERN
- 35. HOW DO WEGET TO CONTINUOUS DELIVERY?
- 36. De Unit tests Integration tests WebService tests Functional UI Tests Manual / Exploratory tests Legend
- 37.
- 38.
- 39.
- 40.
- 41.
- 42.
- 43. TAKEAWAYS – TOGET 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.