Code Smell 272 - API Chain | HackerNoon
Briefly

When testing an API, avoid making unnecessary multiple requests to validate a single operation. This adds complexity and slows down test performance.
Instead of checking resource creation through a GET, focus on primitive steps and validate the POST status directly.
The ideal test should fail in isolation when there's a behavior issue, not due to unrelated operations failing in a chain.
By simplifying test logic and avoiding extra API steps, you can create more maintainable tests with clear, accurate outcomes.
Read at Hackernoon
[
|
]