Pushing The Boundaries Of Continuous Integration
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Pushing The Boundaries Of Continuous Integration

on

  • 4,602 views

Presentation from Agile2008.org of the session 'Pushing the Boundaries of Continuous Integration.

Presentation from Agile2008.org of the session 'Pushing the Boundaries of Continuous Integration.

Statistics

Views

Total Views
4,602
Views on SlideShare
4,564
Embed Views
38

Actions

Likes
2
Downloads
48
Comments
0

3 Embeds 38

http://blog.iclutton.com 30
http://www.slideshare.net 5
http://www.linkedin.com 3

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Pushing The Boundaries Of Continuous Integration Presentation Transcript

  • 1. Pushing the Boundaries of Testing and Continuous Integration Fabrizio Cannizzo Raghav Ramesh Robbie Clutton
  • 2. http://flickr.com/photos/zoonabar/159442457/ Who are we? http://flickr.com/photos/kerrybuckley/ 1356791754/in/pool-web21c
  • 3.  
  • 4. Agile to the Core!
      • XP/Scrum
        • - TDD
        • - Pair programming
        • - Continuous Build/Integration
          • Unit/Acceptance Test
          • Reporting
    •  
  • 5. Feature completeness != completed product http://flickr.com/photos/mattimattila/2188826561/
  • 6. What's Missing?
    • Robustness
    •  
    • Performance
    • Scalability  
    • Failover
  • 7. We needed to know the thing would stand up http://flickr.com/photos/alan-light/2435511982/
  • 8. But we didn't want to wait for formal QA testing
  • 9. We had to last three spooky nights http://flickr.com/photos/luchilu/677786684/
  • 10. After four weekends, we were done http://flickr.com/photos/22243977@N06/2457787000/ Bugs Memory Leaks Poor Environment Log Extractors
  • 11. What next?
    • Create scenarios
    •  
    • Define expectations
    • Automate 
    • Continuously test
  • 12. So... how does it really work?
  • 13.
    • Technologies
      • Cruise Control
      • Java Spring Framework
      • Hand crafted Java code
      • JMX Console
      • UltraMonkey
      • SIPp
      • JainSIP
      • Mockphones
  • 14. Cruise control is the engine that continuously runs typical usage scenarios. http://flickr.com/photos/_fxr/2142296214/ Ensure the entire scenario played out as expected http://flickr.com/photos/mike-burns/35534789/ connect connect join
  • 15. Why are scenarios relevant?
    • Robustness
    • Performance
    • Scalability
    • Failover
  • 16. We automated phone behaviour using SIPp... Different  configurations are implemented using different spring application contexts and network setups Scenario runners are java applications Scenarios are POJOs loaded from spring application context
  • 17.  
  • 18.  
  • 19.  
  • 20.  
  • 21. TestRR
      • Generic Framework
        • Robustness
        • Performance
    •  
      • http://code.google.com/p/testrr/
  • 22. Who else is talking about this?
    • James Bull - Pragmatic Performance Testing - http://is.gd/SUv
    •  
    • Dr. Dobbs - Continuous Integration and Performance Testing - http://is.gd/12Ds
    • Manfred Lange - Introducing Automated Performance Testing - http://is.gd/SUj
    • Paul King & Dalton Cranston – Open Source Performance Testing Tools For The Web
  • 23. What we have learned that you could take away...
    • Automate early and often unit and acceptance tests are an essential first step maintaining these builds can have severe impact on velocity the customer must buy in: formulate user stories to drive the creation of tests
  • 24. ... and also...
    • This drives creation of robust code earlier Leverage existing frameworks for performance testing Build up testing strategies incrementally These tests are resource hungry, use an appropriate environment
  • 25. Q & A   Fabrizio Cannizzo:  - http://smartrics.blogspot.com Raghav Ramesh: - http://ragstorooks.wordpress.com Robbie Clutton: - http://blog.iclutton.com Aloha SIP A/S: https://trac.osmosoft.com/Aloha Web21C SDK: http://web21c.bt.com