Careful - APIs Inside: Testing and Monitoring for App Development
•
4 likes•3,275 views
This document discusses the importance of testing and monitoring APIs that power applications. It notes that apps often depend on backend APIs and problems with APIs can waste development time or even kill apps. It then provides recommendations for tools to help with API development and operations testing, including HTTP sniffers, OAuth libraries, documentation sites, monitoring services, and API-specific analytics platforms. The goal is to make working with APIs easier so developers and providers can have more fun and be more profitable.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Careful - APIs Inside: Testing and Monitoring for App Development
Similar to Careful - APIs Inside: Testing and Monitoring for App Development (20)
More from 3scale
More from 3scale (20)
Recently uploaded
Recently uploaded (20)
Careful - APIs Inside: Testing and Monitoring for App Development
- 1. Careful - APIs Inside Testing and Monitoring for API Driven Apps Steven Willmott 3scale Inc. @njyx, @3scale
- 2. Behind (Almost) Every App is a Great API
- 3. 3scale is… API Infrastructure Provider ! Power 350+ APIs ! 110,000 Developers writing Apps (Selection) ! API Tech Operations API Business Operations Developer Support 3scale.net
- 4. Apps Depend on API Backends Your App Direct Indirect Proxy Your Backend
- 5. Creates Problems Development Time Run Time OAuth Bad Docs Weird HTTP Errors Rate Limit Problems High Latency Version Changes APIs Can Waste Time Old Versions Random Failures Poor SDKs Rate Limit Failures APIs Can Kill Your App
- 6. Development Time Tools HTTP Problems • • • • ! HTTP is Easy until it’s not (Caching, Verbs, Headers, Hashes, Media Types) Use HTTP Sniffers (HTTPScoop, Fiddler) + network sniffers (e.g. Wireshark) Check & use caching headers CORS, Cross Site Problems HTTPScoop Auth Problems oAuth Libraries & Documentation • beware oAuth “variants” • Try: • oAuthbible.com • oauth.io • Other Authentication: • Try to use provided SDKs • Unit Test heavily for custom integrations • http://www.slideshare.net/synedra/demystifying-restruby
- 7. Development Time Tools Provider Problems • • • • • ! Bad Documentation: look for interactive docs (swagger active docs, iodocs, apiary) Unspecified Rate Limits (when do they kick in?) Old Versions Different Production and Test Environments Unit test mocks Pro Tip How to ask An API Provider a ! question ! ! “I was doing the following with you API, I was expecting this … to happen, to my dismay, this other thing happened instead …”(*) (* - credit Kirsten Hunter)
- 9. Operations Time Tools The Old • • • • Pingdom et. al. Provide standard HTTP alerts, Webmetrics: step by step test execution primarily for SOAP APIs Nagios, Monit, Munin, SENSU etc. in your own infrastructure Splunk et. al. for log analysis. ! The New ! How to ask An API Provider a ! question ! • • • Runscope Smartbear 3scale APITools ! • ! New tools: proxy transform, step by step unit testing, authentication tests, API specific analytics ! ! ! http://www.soapui.org/Dojo/overview.html
- 10. Where is the Fun & Profit? API Testing is getting easier APIs are more stable over time Mocks & Proxies Help a Lot Happy Users are More Fun & Generate More Profit!
- 11. Thank You Contact: http://www.3scale.net @njyx - steve@3scale.net