Module 10 of 10

Testing, Monitoring & Governance

Lessons

About This Module

The final module is about keeping an API trustworthy over the long term: proving that it works, seeing how it behaves in production, and making sure its design stays consistent as more people and teams build on it.

It starts with testing: writing automated API tests that check status codes and response bodies, and contract testing, where consumers and providers agree on what an API promises. From there it covers monitoring and observability, using logs, metrics, and traces to spot problems and find their cause. It closes with governance: shared style guides and automated linting that keep naming, errors, and conventions uniform across every API in an organization.

When you finish the lessons, move on to the Projects to put everything from this course into practice by designing and documenting an API of your own.

Lessons

4 videos
01

Postman Tutorial - How to write Automated API Tests in Postman (PART-1)

How to create simple tests for API requests in Postman using JavaScript and the built-in code snippets.

02

Consumer-driven contract testing using pact

A quick introduction to consumer-driven contract testing, with a simple example using Pact.

03

Observability Crash Course: Logs, Metrics, Traces Explained

A walkthrough of monitoring vs observability and the three signals of logs, metrics, and traces, along with OpenTelemetry and SLOs.

04

API styleguide tour

A tour of how to enforce API consistency with a style guide, making your APIs easier for developers to consume.