First view Postman’s performance testing feature
Recently postman released an enhancement for performance tests. It’s currently available on demand through early access. This access is called Postman Canary. If you wish, you can read the development details by accessing from the link below. In this blog, I will only talk about how the related development will be used by me in QA tests and share my first impressions.
https://blog.postman.com/early-access-to-postman-api-performance-testing/
Without straying too far from Postman’s previous elegant and simple operation, they seem to have made it easier to trigger performance runs at the relevant endpoints if desired. For performance runs, a simple interface was designed where the number of threads, test duration and ramp up values can be entered. The interface can be observed in the photo below.
They have also made it easier to interpret the harnesses separately with the filters they have added.
We can also successfully use environment variables when triggering scripts.
Unfortunately I have not been able to experiment with Newman custom reports at the moment, but with newman custom reports we can get even better results.
My comment:
I’ve been actively using postman during backend testing and with this enhancement I think I can monitor the performance side when running tests.
Expectations:
- I would expect them to support parallel execution like other performance testing tools. Who knows, maybe they will include this in future developments.
- I observed that the sent request and returned responses were not written anywhere.
- I would also expect to be able to enter the expected values into the relevant endpoints and if they are met, I would expect to observe this in the report section.
