Extending Continuous Integration
•Download as PPT, PDF•
5 likes•355 views
The document discusses extending continuous integration practices to include more thorough automated system testing. It proposes automating the installation, integration, simulation, and verification processes to continuously test the full system after every code change. This helps find defects earlier but cannot replace traditional testing. The approach aims to pay more for testing now through practices like automated staging to avoid larger costs later from bugs. The ultimate goal is to enable releasing new code every iteration through these extensive testing practices.
![About the speaker ,[object Object],[object Object],[object Object],[object Object],[object Object],.meetup.com/13](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Extending Continuous Integration
Similar to Extending Continuous Integration (20)
More from Johannes Brodwall
More from Johannes Brodwall (16)
Recently uploaded
Recently uploaded (20)
Extending Continuous Integration
- 3. What’s the point of Continuous Integration?
- 5. What is Continuous Integration?
- 10. Result:
- 11. Every check in is is now tested
- 13. Will this find all our defects?
- 14. No!
- 16. So what should we do?
- 17. (Hint: CI is about paying now to avoid paying later)
- 18. Pay more now!
- 19. Our approach: Automated system test
- 23. ” Did you meet any problems?”
- 24. No
- 27. Installation
- 30. Integration
- 31. Integration Dealing with dependencies
- 33. Simulation
- 34. Simulation Put realistic load on the system
- 35. Simulation Depends on what you system does
- 37. Verification
- 38. Verification Finding out if it worked
- 42. Date
- 43. Number of files
- 44. Okay
- 45. Missing
- 46. Extra
- 47. Extra Mismatched
- 48. Extra Extra Extra Known deviations
- 51. Result:
- 52. Every build is now system tested
- 54. Will this find all our defects?
- 55. No!
- 62. Only when you can think as an operator, can you master your system
- 63. Result:
- 64. Every release is hardened
- 66. Will this find all our defects?
- 67. No!
- 69. The goal: Release after every iteration
- 71. The sad reality: Pilot release after every iteration
- 72. Pilot production
- 73. Why releases every iteration?
- 75. Result:
- 76. Find all the bugs cheaply!
- 77. Make sure it always works
- 78. Pay more now to pay less later
- 79. The goal: Release after every iteration
- 80. (And throw away the bugtracker)
- 81. Thank you!