We did not previously use a different solution. 

We have been using Postman from the start as it is user-friendly and does not require any prerequisite language to use it.

I also work with ReadyAPI. ReadyAPI is a more advanced tool than Postman because a lot of heavy data can be driven and a lot of test cases can be automated and triggered on a daily basis. That's how I worked with ReadyAPI. Postman is more of a manual effort tool, whereas ReadyAPI is more of an automation tool. It did have the option of scripting in Java or JavaScript, but I just worked with Google Script with ReadyAPI. So, I haven't worked on any other programming language with ReadyAPI, and I'm not very sure whether it supports any other languages such as Python or JavaScript. Other than that, it works very well for regression cycles. Getting the email-triggering functionality was also very good. If you want to have a lot of automation and run it on a regular basis, it's one of the recommended tools.

We used UFT earlier.

I started with SoapUI. It is similar in terms of capabilities and functions. There was no specific reason for switching to Postman. I saw people using Postman more, so I started using it. 

Postman is more popular than SoapUI. When we are doing testing of the APIs that we want to consume, people usually say that this is a Postman request, and you can try it out. More people use Postman than SoapUI, and that was the reason I started using Postman. 

I use Selenium as a web development tool and testing tool. I also use Azure Database for MySQL.

I have experience with SoapUI. The environment where I work for the moment is more Postman-oriented. In the past, some government departments in Belgium were using SoapUI. Postman is similar to SoapUI. The features in SoapUI, for instance, the automated testing features, are things that I don't need at the moment. Postman performs how I like it.

We have also worked with SoapUI, but we like Postman because it has automation.

Postman is a more compact tool, and it has many functionalities. In the first stage that we used, Postman, we only tested how it works. Now we are using more functionalities. With SoapUI, it's because some customers have used it to define the APIs, and then we have to interact with this environment.

But we use Postman, and we prefer Postman. Although, there are some tools from SoapUI that are good. For example, the API design, checking, and definition. If Postman has anything similar, you can check the definition of the API, and it proposes you an improvement and so on, but in the development phase, we used Postman, and we like Postman.

We also used LoadRunner to do some testing but that is for entirely different purposes. It's a load-testing tool for performance, whereas Postman is used more for functional testing. We mainly use Postman mainly to when a thing has occurred in your form. So when we're doing integration testing and all that, we use Postman. It is almost like a manual test where the processes are entirely different. For other purposes, we use tools like LoadRunner, Jenkins, and JMeter. We also use Selenium for automation testing and to execute our CFPB pipeline division. 

We chose this solution based on the project. Typically, the client requests something, and, depending on the client and the project's needs, we'll use what makes sense. We use the best tool for the job. If it happens to be this solution, then we use it. If it's something else, we use something else. 

Given an opportunity, I would prefer to use Postman over SwaggerHub. People mostly prefer to use SwaggerHub over Postman.

We use quite a few products from an infrastructure point of view. We use SolarWinds, both for server and infrastructure capacity, and we use a change management and a problem management tool. From a bandwidth monitoring perspective, we use a network analyzer; we use Splunk heavily. We do a lot of scripting tools using Postman and Python.

I'm more into Python since Python gives us many more API interjections and compatibility with a lot of other APIs. We started using Postman, and then we immediately moved to Python-based scripting.

The functionality that Python gives you concerning the available APIs and then the ability to put that in the Excel sheet is much better than Postman.

We do have another tool. We are using Jmeter, among others. However, I do not like its look and feel. Postman allows for saving collections and has a nice look and feel. 

I have used Apache JMeter previously.

I have used Swagger. I would recommend Swagger for the backend developers. The APIs only need to be set up once, then Swagger generates the document for all of them. In Postman the APIs need to be set up manually.

I used SoapUI previously. I found Postman to be more interactive and accessible compared to SoapUI.

We've used other solutions in parallel with Postman, like ADAPT Test. ADAPT is more of a service virtualization tool, but we can also do API testing in that particular tool. We were finding it difficult because it taking time for us to open the tool. Frequently, we were getting some error messages. On the other hand, we had support. It's a good tool, but it was not that stable. Eventually, we decided that we would just stick with Postman.

I have used Swagger and SoapUI. SoapUI does not have API automation. Postman is better than SoapUI when it comes to usability.

I have not used a similar solution to Postman.

We didn't use any other solution before Postman. A senior developer suggested Postman.

We previously did not use other solutions.

We did not use another solution prior to this one.