Programme Launch Offer: Save 20% - Book Now

Track Talk, T23

Testing Beyond Your Product

Megan Ozanne

16:45 - 17:30 CEST, Tuesday 16th June

I remember once towards the start of my career an issue came over from the support team that was causing a lot of pain for one Client ( the entire app kept crashing ). The support team had spent a month trying to diagnose the issue, to no avail.

The issue came over to the test team and I was eager to get stuck into this challenge. I spent a couple of days trying to run through all the edge cases I could think off, race conditions, even testing in the Clients own environment.

It wasn’t until I took to sites such as Stack over flow and did some research into the limitations of some of the third parties that we integrated with that I found the issue. It was a specific issue that you hit in a scenario that this one specific Client was encountering and through the research I did we were able to put a fix in.

This specific scenario highlighted the need, early in my career to test third party integrations, even at times when I have been advised not to waste my effort. That’s why I want to submit this abstract for a talk that explores the hidden costs behind third party integrations and testing strategies for them. This talk will equip attendees with practical techniques to ensure their app remains robust, even when dependencies don’t.

What I will cover

* The importance of considering how third parties affect your product.
1. Why third parties integrations are risky
* How to test third party integrations
1. Contract testing and schema validation
2. Mocking vs. stubbing vs. sandbox environments
3. End-to-end tests with real integrations (and when to use them)
4. Chaos testing and fault injection
* How to approach bugs within your product caused by third parties