"5 Myths about API testing: There's more than meets the UI"

APIs Everywhere and Here to Stay A few years ago, we entered the era of mobile computing But that came with some challenges: Many devices, many networks and many connections. Apps connect devices to vast amounts of servers and data through complex APIs. How do you ensure that the APIs work as planned? API failure means your apps fail, and your quality and reputation take a direct hit that flows to your bottom line API Testing reduces the business risk of faulty APIs

Every App Has its API…to Test Enterprise apps rely on a myriad of internal, external and public APIs Testing APIs must include different networks, end-points and interfaces Test Scenarios Then Now The fact that an API is published does not decrease the test scenarios required; it increases test scenarios in all dimensions

Myth #1 about Testing APIs If it’s a published API, it’s been tested and guaranteed. No further testing required. Just because an API is “published” does not mean that the API has been tested with anything, particularly your custom applications Public APIs, even the few with SLAs, are the responsibility of third parties – you may trust them, but you must verify them, with API Testing MIND THE GAP You cannot afford to overlook the gaps in testing APIs with your applications

Interesting, right? This is just a sneak preview of the full presentation. We hope you like it! To see the rest of it, just click here to view it in full on PowerShow.com. Then, if you’d like, you can also log in to PowerShow.com to download the entire presentation for free.