How to Test When You Have The Keys to The Castle

Reliable testing of third party services and micro-services can be tricky. You can always write integration tests, but those are only as good as they are maintained, and as good as the mocks that define them.

This talk describes how to evaluate the best testing strategy for a handful of third party services and micro-services, when you have the ability to change how they are implemented to allow for better test coverage. We’ll cover third party services that handle billing, google metadata, and sending text messages as well as micro-services that do AI text analysis, data scraping, widget and pdf creation.

By the end of this talk, you will be able to create your own testing strategy for these kinds of services, and have confidence in your tests when the code for the services is changed.

 
 

Outline/Structure of the Case Study

First I will define microservices. I'll also explain a couple of key concepts when talking about services, like mocking

Then I'll go through a handful of techniques for testing microservices and 3rd party services

Learning Outcome

By the end of this talk, you will be able to create your own testing strategy for these kinds of services, and have confidence in your tests when the code for the services is changed.

Target Audience

Anyone involved in an end-to-end test suite

Prerequisites for Attendees

Basic knowledge of system architecture. Experience with testing 3rd party components, or microservices

schedule Submitted 10 months ago

Public Feedback