Postman Primary Use Case

reviewer1369950
Software Quality Assurance Engineer at a tech services company with 51-200 employees
Our primary use case for Postman is API testing for our product. We haven't automated the request and response part yet, like how we used to do for automation scripts. Basically, we are just shooting the URL's and recording the response. As of now we have multiple API's and we are using the collection so that we can run it together in a single flow, like an automation execution. Then we use the basic variables and the collection variables. We even saw that we have some additional validation through the response code and the status code, like if there is an expired date then we should be expecting 200 status codes. We are doing those kinds of things now. We have been using Postman for the API testing for two to three month. View full review »
Girish Khileganvi
QA Lead at a tech services company with 5,001-10,000 employees
Almost all the teams here depend on the APIs, which are built-in SOAP or JSON. We have multiple teams testing JSON and they use Postman. There are multiple applications teams that integrate their interfaces with APIs, and they use the Postman. View full review »
Deepanshu Joshi
Software QA Test Engineer at a tech services company with 201-500 employees
We are using Postman for our testing and checking our API response and validations. View full review »
MichaelDu Preez
Senior DevOps Engineer at a tech services company with 201-500 employees
My primary use case is for API testing. View full review »
reviewer1271004
Programmer Analyst at a university with 5,001-10,000 employees
My primary use case is for responses. I'm a user and work as a programmer analyst. View full review »