PactFlow for AWS

My main use case for SmartBear API Hub  is for API automation.

A quick specific example of how I use it for API automation is that we usually run regression testing, where we are using API URLs and we are using property transfer steps and we are also using database testing as well using JDBC connection. We are validating the responses for status code and some validations that give us confirmation that our API is currently working. We are working on an insurance company, so we are validating the insurance details, the claim management system, and the claims that the particular person is raising. We are validating it from the UI as well as from API. For API automation, we are using ReadyAPI  and for UI, we are using some other tool. We are also integrating the UI automation plus API automation in a single test case using Chrome DevTools protocol with ReadyAPI  as well. We are creating a regression suite, validating the quick responses, and the smoke testing as well where we are validating the status code of particular APIs.

We are using ReadyAPI for API automation and database testing as well, where we are validating our certain documents are in the database or not or our transaction key is in the database or not that is being triggered by API and we are validating it from the database using the JDBC connection.

The best features that SmartBear API Hub  offers in my experience are that it is really easy to create a regression suite, it is very easy to connect with a database, and it is very useful in data-driven testing as well where we are using property transfer. You can create variables at the test folder level or the test case level and you can use it in your API. This is helpful for data-driven testing and connection with the database. You can also integrate Chrome DevTools protocols there so that you can also validate dynamic values from UI as well as from API. This allows you to create a whole regression suite.

I find myself using database testing and data-driven testing more because we are an insurance company, so we have a regression suite that is primarily on the data.

SmartBear API Hub has positively impacted my organization as it helps to create our regression suite as well as connection with Jenkins  to run smoke testing and regression settings. It saves a lot of time and it is one tool for every testing. It helps us to create a regression that covers most of the scenarios for our company, and that is why we are using it.

I have noticed some errors regarding the connection with Bitbucket  or Git . It generally takes some time in SmartBear and ReadyAPI. From the testing perspective, it saves a lot of time because it covered a whole regression suite with database and data-driven testing. It generally saves us time from fetching the values manually from UI. Instead, you can run your regression suite on a daily or weekly basis. This helps us to identify some errors as well as saves us time.

There is a delay in connection with SmartBear API Hub; sometimes the connection is lost between the Bitbucket  and ReadyAPI. When we try to reconnect those from the properties level, from the setting level, it generally takes a lot of time. This perspective can be improved with the Bitbucket and Git  connection. We can also integrate a particular framework in ReadyAPI itself so that we can also run our Selenium code from the UI automation perspective. Right now, we are currently using that feature, but it requires framework-level changes. We can provide it to every user so that users can easily run their Selenium scripts, fetch the APIs, and validate the database. This helps us to create one-to-one end-to-end flow for the purpose of testing. We can enhance that feature and we can also enhance the Git functionality because we are using Sourcetree as well for connecting Bitbucket and ReadyAPI in order to push and pull our changes. That particular functionality takes a lot of time. Sometimes the changes that we have made in our regression suite are not reflecting on the recent changes in ReadyAPI. This is sometimes difficult to track and takes a lot of time to refresh that. I would say we should enhance the UI automation feature and we can also enhance the Git connection feature as well.

I have been using SmartBear API Hub for one year.

SmartBear API Hub is stable.

In terms of scalability, I think we can increase some more features. As I mentioned, the UI automation part can be enhanced. We can also increase capabilities to connect with different kinds of databases including MongoDB. We can improve by integrating more advanced SQL features in our JDBC connection so that we can also run our queries and manage the database there. The feature is still present, but we can improve in that way by connecting to MongoDB and connecting to different databases at a very easy level. We can also increase the validation aspect. For example, if I want to create a dynamic value or generate a dynamic variable, we could have that feature in ReadyAPI.

Customer support is good; I have not connected to any of the customer support teams, but from the past experiences with our colleagues, it is good.

Before choosing SmartBear API Hub, we were previously using Tosca for API automation, but we are relying on ReadyAPI because of its features that I mentioned, including easily Git connection capabilities and database connection capabilities, as well as data-driven testing. That is why we switched from Tosca to SmartBear API Hub.

I have seen a return on investment; previously we were using five resources for automation testing, but right now, using SmartBear API Hub, we can easily create a regression suite, and that is reduced to two resources.

Regarding my experience with pricing, setup cost, and licensing, when a person is in training, we usually get a free license for some days. After the person is trained, we get a valid license for that amount of time. Overall, I think my experience with cost and pricing is good.

My advice for others looking into using SmartBear API Hub is that it is very easy to use and easy to create a workflow for end-to-end testing. It is good for that. It is also available for contract testing as well. We can increase the contract testing feature in ReadyAPI so that people can start working on the contract testing feature. Generally, we are validating the schema level, YAML files, and we are also validating. We can improve in that area if something changes in the YAML files. We can also enhance the validation and contract testing feature in SmartBear API Hub. Currently, we are just validating the responses against the particular YAML, but we can also improve that.

Regarding SmartBear API Hub's AI capabilities, I think its governance and security are pretty much good, and we are also relying on SmartBear API Hub for AI capabilities, which also serve as a good add-on feature. It helps to improve our efficiency.

Regarding SmartBear API Hub's AI capabilities, I find its reliability and accuracy to be really good. It has a lot of AI capabilities that can enhance our efficiency. In terms of accuracy and reliability, it would be a 10 out of 10. I do not think any changes are needed in that area.

I would rate this review an 8 out of 10.

My main use case for SmartBear API Hub  is that I was looking for a better tool in the market that can handle everything from documentation to contract testing, to API testing as an independent tool rather than hopping from one tool to another just for its own greatness.

A quick specific example of how I use SmartBear API Hub  in my daily work is that the biggest advantage I felt SmartBear API Hub has is its ability to validate contracts for APIs we have created in my project.

I don't think I have anything else to add about my main use case; I guess that was the biggest advantage we wanted to gain from this particular tool.

I developed a Proof of Concept utilizing the SmartBear API hub, and I was particularly impressed by the platform's ability to consolidate all aspects of the API lifecycle—from documentation and governance to security, development, and testing—within a singular, integrated environment.

SmartBear API Hub's best features are its governance, spec-first design, contract testing, overall dev experience, documentation, and, best of all, testing integration.

The governance feature helps my team by automatically enforcing rules on how APIs are designed and maintained before bad APIs reach production, which is a standout for SmartBear API Hub.

I want to add that the best part was getting a single platform where we can do everything from governance to contract validation to development to testing in one tool instead of hopping around, and I think that's the best feature anyone could ask for.

SmartBear API Hub has positively impacted my organization because I created this POC, and my upper management was really happy, and eventually, we'll start rolling it out for other projects too.

After using SmartBear API Hub, I've noticed we've saved a lot of time, which was a problem with our old tools, so time-saving was our biggest achievement.

I don't think I'm the right person to say how SmartBear API Hub can be better since I want to spend more time checking it out before just blurting out suggestions.

So far, so good, and I don't really have any complaints about what needs to be improved.

I have been using SmartBear API Hub for around a year.

SmartBear API Hub is stable.

Regarding the scalability of SmartBear API Hub, we have consistently found it to be perfectly adequate for all project requirements to date.

My experience with customer support has been positive; so far, so good, with no complaints.

I previously used Postman and REST Assured APIs in my project to automate and test our test cases, and we were just looking for a better tool that could handle everything rather than switching from one tool to another.

Straight forward!

No

I've seen a good return on investment with SmartBear API Hub, mostly because of the time it saved me. But since that's out of my hands, I'm probably not the best person to answer this question.

My experience with the pricing, setup costs, and licensing has been positive, as these expenses were covered by my company, resulting in a mutually beneficial outcome.

I didn't check out other options before picking SmartBear API Hub because someone told me about it, and I actually wanted to try it since I was really impressed that it's a single platform that handles everything, so I didn't need to jump to any other tool.

I would give SmartBear API Hub an eight out of ten, but as I just mentioned, I still need to explore it more.

I chose an eight because what if I haven't yet explored all hidden features? So, whatever use cases I've used from this particular tool, I'm still in a position to give it an eight, but for sure not a ten as of now.

Regarding SmartBear API Hub's AI capabilities, I believe its governance and security are important because as AI coding tools increase development velocity, APIs are generated, modified, and consumed faster than ever, often without sufficient visibility or validation, and SmartBear's governance closes these gaps.

I think SmartBear API Hub's AI capabilities are effective as they eliminate "zombie APIs," such as undocumented and unmanaged endpoints that increase attack surfaces. Also, distributed teams create silos in API development and multi-gateway requirements, making standardization difficult, so governance centralizes that control.

I would advise others looking into using SmartBear API Hub that if people have a time crunch and don't want to discover or experiment with multiple tools, then I think this particular tool is a one-stop solution.

I don't think I have any additional thoughts about SmartBear API Hub before we wrap up; I'm good. My overall review rating for SmartBear API Hub is eight out of ten.

My main use case for SmartBear API Hub  involves reviewing the API documentation and OpenAPI Swagger specifications provided by the developer so I can understand the request and response schemas. Along with that, I validate the API behavior and create automation test cases using Playwright and Python, which is the current framework we are using, and I also check if it is aligned with the API contract given by the development team for testing.

As an automation test engineer, I use SmartBear API Hub  to review the API specification provided by the developer. Before implementing automation tests, for example, when a new API endpoint is introduced, I refer to that API documentation to understand more about the request, response, headers, and how authentication is required, as well as what the expected response I will get. I create API automation tests to validate the functionality, handle error handling, and ensure data integrity properly. These are the things I do in day-to-day work when I get a new API change or API request from the developer.

The best features SmartBear API Hub offers include a centralized API documentation system, much in the way Swagger or OpenAPI provides, which I find most useful. We mostly use the Swagger specification for management and version control for the APIs, and we have moved from version 1.0.0 to 2.0.0. This is great because we can see and validate what the previous version and the latest version are, and how the schema has changed. Having a single source of truth for API contracts makes it easier to understand the request and response schemas, keeps automation test cases aligned with the API changes, and reduces misunderstandings during the development and testing cycle. The clear API documentation also helps speed up the onboarding and troubleshooting processes for us.

In addition to the best features, the ease of use in SmartBear API Hub is significant, and the collaboration aspect is very useful. It helps the developer and QA teams to work from the same API specification, reducing ambiguity and improving communication when any APIs change or are newly introduced. The interface is straightforward and easy to navigate, making it simple to find endpoint details, request schemas, and responses.

SmartBear API Hub has positively impacted my organization by improving collaboration between the development and QA teams through a centralized source of API documentation and specification. This has reduced misunderstandings around the API contract and helped our testers to understand changes more quickly, enabling the faster creation of automation test cases. Having a clear, up-to-date API definition has also reduced the time spent on various processes.

While SmartBear API Hub is mostly a useful platform for API documentation and collaboration, there are opportunities to improve it by implementing more advanced search and filtering capabilities. This would be particularly helpful when looking at hundreds of API endpoints. Improving the reporting and change tracking features would also help the team identify updated API contracts, along with deeper integration with testing in CI/CD tools and AI integration in SmartBear API Hub.

Performance-wise, I have not felt any slowness in SmartBear API Hub, but it would definitely be good if it is improved further. I would want to see user experience enhanced, as navigating a large collection of APIs can sometimes be challenging. Improving search functionality, which I mentioned as feedback, and allowing dashboard customization would make it much easier to find information. Additionally, optimizing performance while working on large API specifications or catalogs would help users access relevant information more quickly and improve overall productivity.

I have been using SmartBear API Hub for around eight or more months now.

My advice to others looking into using SmartBear API Hub is that it is definitely good for API designing, documentation, and governance processes, and to get the most value from the platform, it is particularly useful for deployment. QA and architecture teams should use it as a shared resource of truth, and maintaining accurate API definitions and encouraging team-wide adoption can improve collaboration, reduce misunderstandings, and make API testing and integration efforts more efficient. The good and bad parts have already been mentioned in my previous responses.