Organizing and structuring tests

As the saying goes, an ounce of prevention is worth a pound of cure. This is good general life advice and is also true in test automation. Taking a bit of time to structure and organize your tests when you are starting will save you a lot of time later, when you are trying to understand test failures or reports on test effectiveness. Postman understands this philosophy and makes it easy to keep tests well-organized.

It is too easy to spout off a bunch of theory that you will skim over and not fully understand. In order to keep this practical, I will try to walk through a concrete example. I will once again use the Star Wars API for this (https://swapi.dev/). So, how would you go about structuring the tests for this API?

Creating the test structure

Let's start with the obvious thing – collections. One way you can think of a collection is as a folder that you can collect items, such as other folders and tests. You may already have...