APIs and testing
By the end of this track you can read and send any HTTP request, build a pretend API with Mock Studio, test a real or mock API with ApiWorkbench, and plan a test suite that catches real bugs. No coding experience is needed.
Who it is for: anyone starting out with APIs: testers, students, front-end developers, product people who want to read what the back end really says. Time: about 2 hours for the lessons, then as much testing practice as you like.
Lessons
Then: test APIs properly
The API testing guides teach the method: what to check in every response, how to plan, and a guide for each kind of test.
Labs
Each lab is a Mock Studio project and an ApiWorkbench collection that work together. Import both and follow the steps.
The apps
| App | What it does in this track |
|---|---|
| ApiWorkbench | The client: sends requests, checks answers with tests, runs collections, load tests, runs in CI |
| Mock Studio | The server: answers with responses you design, and misbehaves on demand |
| Developer Toolbox | Decode a JWT, format JSON, convert Base64 while you test |
See ApiWorkbench and Mock Studio together for six ways the two apps work as a pair.
Related tracks
- Networking and SSH: what is underneath every request
- Security and safe habits: keeping tokens and keys out of trouble
- Databases: checking what an API really wrote