How to release every week case study of continuous integration
0 likes402 views
With a legacy system, the team releases weekly by having 70% unit test coverage and 1500 acceptance tests using Robot Framework, with testing via regression flows and keeping delta technical debts to 5 days or fewer while avoiding critical issues through practices like test-driven development and pairing/mobbing as feasible given the legacy code base.
1 of 17
Download to read offline
More Related Content
What's hot (12)
Ad
Viewers also liked (18)
Ad
More from Tung Nguyen Thanh (10)
Recently uploaded (20)
How to release every week case study of continuous integration
- 1. How to release everyweek With legacy system
- 2. HUNG HOANG Tech Lead CHAU HOANG Agile Coach
- 4. XP
- 5. LEGACY SYSTEM Where it all began
- 7. Image courtesy of The-Challenge.org
- 8. CODE Partially owned TEST Must be fully covered FEATURES Adding as you go DEPLOYMENT Big Bang Forbidden
- 9. Approach
- 10. How things are stored
- 11. Workflow User Stories Tasks Development Deploy Staging/ProductionPackage Repo Repo
- 12. Testing via RF
- 13. Current Stats 70% UNIT TEST COVERAGE 1500 ACCEPTANCE TESTS 5days DELTA TECHNICAL DEBTS 0 CRITICAL ISSUES
- 14. Issues • TDD as you wish • Legacy acceptance tests • Difficult test setup • Conflict with vendor • Pair/trio/mob mess
- 15. Robot Framework
- 16. WE’RE HIRING
- 17. Q&A