Modern web applications often rely on internal APIs, multiple frontend applications, several third-party services, and dozens of vendor libraries. With complex distributed systems like this, how can developers create a comprehensive test plan that covers everything without slowing development down to a crawl?

In this talk, we'll learn how to create test plans for complex, service-oriented applications as well as some best practices for testing across a distributed architecture. We'll see how layers of unit, integration, acceptance, and end-to-end tests can greatly improve the reliability of our applications and make maintaining them much easier in the long-run.

Slides: https://drive.google.com/drive/folders/0B2SL8f3YPEJPLUdTWVZ2MEotMmc

Given At:

- [API Strat and Practice, 2017](https://apistrat17.sched.com/event/BiDd/testing-layers-in-a-distributed-architecture-karl-hughes-the-graide-network) ([Video](https://www.youtube.com/watch?v=NcQryexNKhM))
- [Codemash, 2018](https://www.karllhughes.com/posts/testing-layers-codemash-2018)
- University of Illinois Web Conference, 2018
- [JS Chi Meetup, 2017](https://www.youtube.com/watch?v=_o5-g4Boe1s&t=9s)
- [Angular Chicago Meetup](https://www.meetup.com/Angular-Chicago-Meetup/events/239758211/)

Blog Posts:

- [Testing Layers in a Microservice Architecture](https://www.karllhughes.com/posts/testing-layers)
- [Why Testing is Important for Distributed Software](https://www.linuxfoundation.org/blog/2017/10/testing-important-distributed-software/)