What's a test pyramid? How can you implement it when talking about HTTP APIs?
A test pyramid describes that when writings test cases there should be a lot more low-level unit tests than high level end-to-end tests.
When talking about HTTP APIs, it may come down to this:
- a lot of low-level unit tests for your models
- less integration tests, where your test how your models interact with each other
- a lot less acceptance tests, where you test the actual HTTP endpoints