Successfully reported this slideshow.

Boulder StaleFish Presentation

1,139 views

Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Boulder StaleFish Presentation

  1. 1. WHO AM I?
  2. 2. Justin Smestad http://www.evalcode.com
  3. 3. justin.smestad@factorylabs.com
  4. 4. SIDE PROJECTS http://github.com/jsmestad
  5. 5. THE UTILITY
  6. 6. born from necessity
  7. 7. fast CI builds Calling live services is slow
  8. 8. avoid breaking TOS Getting blocked for too many requests is annoying and potentially expensive (monetarily)
  9. 9. clarity canned responses means anyone can see what a response SHOULD look like [w/o docs]
  10. 10. avoiding stale data unreliable APIs mean that the service response could change any time without notification
  11. 11. StaleFish http://github.com/jsmestad/stale_fish/tree/master
  12. 12. FEATURES
  13. 13. framework agnostic just drop it in already
  14. 14. RSpec
  15. 15. Test::Unit / Shoulda
  16. 16. yaml configuration #{RAILS_ROOT}/config/stale_fish.yml
  17. 17. specify fixtures StaleFish.update_stale(‘google’, ‘github’, ‘omniture’)
  18. 18. optional force flag StaleFish.update_stale(:force => true)
  19. 19. UPCOMING FEATURES
  20. 20. FakeWeb use stale_fish config to optionally manage your FakeWeb stubs.
  21. 21. manual build trigger via CRON kick off intermittent CI task weekly/monthly to ensure fixtures are still valid.
  22. 22. rake task StaleFish from command-line
  23. 23. Resources ✤ GitHub Project: http://github.com/jsmestad/stale_fish/tree/master ✤ Wiki: http://wiki.github.com/jsmestad/stale_fish ✤ Twitter: http://twitter.com/jsmestad ✤ AIM: justin.smestad@gmail.com ✤ Blog: http://evalcode.com

×