Download as PDF, PPTX
Uploaded byAnand Bagmar
Enabling CD in Enterprises with Testing
The document discusses enabling continuous delivery in enterprises through testing, highlighting challenges such as team distribution, integration, and defect management. It emphasizes the importance of continuous integration and delivery as practices that allow teams to release software frequently and receive prompt user feedback. The content also covers test automation strategies and environments necessary for efficient testing and integration.
More Related Content
Similar to Enabling CD in Enterprises with Testing
Enabling CD in Enterprises with Testing
- 1. ENABLING CONTINUOUS DELIVERY IN ENTERPRISESWITH TESTING Anand Bagmar Test Practice Lead
- 2.
- 3. WHAT DO YOUEXPECT FROM THIS SESSION?
- 4. A Triangle =A Pentagon
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14. EXECUTION CHALLENGES Multi-Partners - Policies - Constraints - Way of working Stakeholders Agile Money! Trust
- 15. OTHER CHALLENGES Team Distribution &Integration Scope Co-Existence Data Migration Defect Management
- 16.
- 17. CODE QUALITY Core product team(s) Customization team(s) Integration& configuration team(s) Systems team(s) NFR Team(s)
- 18. How to getearly feedback in such situation?
- 19.
- 20. 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
- 21.
- 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.
- 24. HOW DO WEGET TO CONTINUOUS DELIVERY?
- 25.
- 26. Test Automation A PRACTICETHAT MAKES TEAMS SUCCESSFUL?
- 27. Test Automation A PRACTICETHAT MAKES TEAMS UNSUCCESSFUL?
- 28.
- 29.
- 30. Why do wedo Test Automation?
- 31.
- 32. How to getquick feedback from Test Automation?
- 33. IDEAL TEST AUTOMATIONPYRAMID Unit Manual / Exploratory Integration JavaScript View Web Service UI Cost Impact Time Business- facing Tests Technology- facing Tests
- 34.
- 35. ICE-CREAM CONE ANTIPATTERN Manual / Exploratory UI Web Service View JavaScript Integration Unit
- 36. Web Service View JavaScript Integration Unit Developers TestPyramid QA Team Test Pyramid DUAL TEST PYRAMID ANTI-PATTERN Manual / Exploratory UI Web Service
- 37.
- 38. HOW DO WEGET TO CONTINUOUS DELIVERY?
- 39.
- 40. LEGEND Unit Tests Integration Tests Web Service Tests Functional UITests Manual / Exploratory Tests
- 41.
- 42.
- 43.
- 44.
- 45. TO GET EARLYFEEDBACK – 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
- 46. So …. A Triangle== A Pentagon
- 47. OR … A Triangle== A n-dimensional Polygon
- 48.