Blocked because the API you depend on doesn’t exist yet or isn’t completely ready? Facing trouble to test various scenarios due to lack of control over third-party APIs? Struggling to test failure cases like receiving an invalid response , 5XX errors and so on? Having flaky tests due to slow API responses?

These are some very common problems we encounter. We cannot rely on slow APIs, which provide a very narrow range of responses. So how can we test effectively in such situations? Is there any feasible solution available? Fortunately, there is: mocking of APIs.

In this session, I will explain how to stub APIs using Wiremock. With a real life example application, we’ll explore how to handle complicated scenarios and form testing strategy. Join this session to gain insights on how, when, and most importantly why we should stub APIs. Let’s find together how development and testing can benefit from mocks.

Shivani is a passionate QA Engineer who believes that knowledge sharing boosts up all engaged parties and increases their confidence. It was summer of 2013 when Shivani and “testing” met each other for the first time and have been best friends since then. Holding rich experience in the testing domain, she currently works as Senior QA Engineer with XING (the largest business network in German speaking countries). With hands-on experience in all layers of software testing ranging from UI(frontend), API and backend, functional, non-functional , mobile testing – API remains her all-time favourite. As a certified scrum master, working in an agile manner is always her approach. She believes in the idea of spreading her findings about any “new fancy stuff” she learns. She has worked with multiple international teams and brings forward the idea of the whole team contributing for quality. She’s always up for conversation over email, linkedin, Xing , twitter or beer table :)

The power of mocking APIs