Downloaded 51 times
Uploaded byJohannes Brodwall
Extending Continuous Integration
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.
More Related Content
Similar to Extending Continuous Integration
![UiPath Automation Suite Installation (Hands-On) [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/automationsuitecommunitysession2-251015095633-a6d862f1-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Extending Continuous Integration
- 1.
- 2. About the speakerJohannes Brodwall Lame duck Lead software architect at BBS Organizer Oslo XP meetup Organizer Smidig 2008 Blog: http://brodwall.com/johannes/blog .meetup.com/13
- 3. What’s the pointof Continuous Integration?
- 4. Pay now toinsure against defects Pay less to deploy to production Release whenever you want
- 5. What is Continuous Integration?
- 6.
- 7.
- 8.
- 9. Unit test Functionaltests System run in test harness
- 10.
- 11. Every check inis is now tested
- 12.
- 13. Will this findall our defects?
- 14.
- 15. Limited to ourtest harness Limited to our imagination And then there’s performance
- 16. So what shouldwe do?
- 17. (Hint: CI isabout paying now to avoid paying later)
- 18.
- 19. Our approach: Automatedsystem test
- 20. Realistic setup Realisticload Realistic variation
- 21.
- 22. How to automatesystem tests Automated build (and test) Scrap old data Install latest snapshot Download production data Replay production data Verify result Send results and logs via email
- 23. ” Did youmeet any problems?”
- 24.
- 25.
- 26. The hard bitsInstallation Integration Simulation Verification
- 27.
- 28. How to automateinstallation Easy, scripted, always working install Simplify (Replace WebSphere with Jetty) (Combine components) Reduce integration All nodes look the same
- 29. (Side effects) Easyinstallation Simpler design Simpler architecture
- 30.
- 31. Integration Dealing withdependencies
- 32. Dealing with integrationDon’t integrate - Do it yourself! Simulate other system Fake responses Keep canned data (data centric) Integrate with test version
- 33.
- 34. Simulation Put realisticload on the system
- 35. Simulation Depends onwhat you system does
- 36. How to simulateproduction In our case: Files Crawler (Dyrkorn & Watne) Load generator (D&W) Record HTTP requests
- 37.
- 38. Verification Finding outif it worked
- 39. How to verifyresults Compare with production Verify integrity Check logs
- 40. Comparing Store testresult in database Store production result in database Full outer join on key fields Find missing or mismatched status Filter out know deviations
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47.
- 48. Extra Extra ExtraKnown deviations
- 49. Consistency checks SQLexpressions that pick out things that are weird
- 50. Logging It matters!Error logs should be empty if everything is okay
- 51.
- 52. Every build isnow system tested
- 53.
- 54. Will this findall our defects?
- 55.
- 56. Limited integration Limitedstability
- 57.
- 58.
- 59. Automated staging ”Next” version Lock-step with production Promote after a week Monitor 9:00-16:00
- 60.
- 61.
- 62. Only when youcan think as an operator, can you master your system
- 63.
- 64. Every release ishardened
- 65.
- 66. Will this findall our defects?
- 67.
- 68. Wrong requirements Poorsolutions New user behavior exposes bugs Bugs we didn’t care enough about
- 69. The goal: Releaseafter every iteration
- 70.
- 71. The sad reality:Pilot release after every iteration
- 72.
- 73. Why releases everyiteration?
- 74. Find more bugsTry the easy solution first Find new requirement faster Exploit opportunity
- 75.
- 76. Find all thebugs cheaply!
- 77. Make sure italways works
- 78. Pay more nowto pay less later
- 79. The goal: Releaseafter every iteration
- 80. (And throw awaythe bugtracker)
- 81.