Postman is an API

Operation is so intuitive that anyone who has already used a developer tool in the browser will get along with Postman straight away. The ready-made test snippets allow you to put together test cases in no time at all, which can explain the failure of a test procedure relatively precisely. Executing from the command line is more of a logical consequence than an additional feature. Thanks to the low hurdle, developers can also start individual tests locally and check their changes immediately.

But where there is light, there is also shadow: in the free version, it is not possible to work properly in teams. In the general, versionable format, the data is only available via export, which however always has to be controlled manually. Some tried to package the Postman data storage folder in a version management system (such as git), but this is generally not advisable - the risk that the automatic merges will create unusable configurations is too great. In its paid version (from $ 8 per month and user), the manufacturer offers exactly this feature of keeping tests synchronized across teams. That's only legitimate, it's a commercial product, after all.

Due to the great freedom in test design using JavaScript, you definitely have to come up with common standards for tests in a team, otherwise the variance increases. In one of our projects, some developers added a check of the status code, response time, and well-formed content to each test, while the rest did not. Adjusting the tests at a later point in time costs unnecessarily time, which is why a style guide for tests should be designed directly with the architecture.

All in all, Postman is and will remain a very good tool. It remains to be seen whether the team functions behave as one would suspect based on the rest of the product. Postman also offers other functions, such as a local API mockup (as well as the same in the cloud) to support the development of clients. Many more features that we haven't been able to examine here.