HyperTest Reviews

Hypertest integration with our applications was pretty smooth from a backend perspective, and the developers were able to access it easily through the Dashboard directly and start with their tests. Also, the UI is very easy to use.This makes it the go-to solution.

Creating Hypertest test cases becomes difficult with production applications with heavy incoming traffic, we have to use a portion of the traffic in such cases to do the test.

API changes can be detected quickly and also used to make sure they are backward compatible. This ensures there are no bugs pushed to production due to any change in API responses.

The best thing about HyperTest is that you don't need to maintain any unit tests for your APIs. Any enhancements or additions to the APIs can be quickly tested, ensuring it is backwards compatible. So this makes sure of free bug-free deployments. The UI is very easy to use.

HyperTest mirrors the requests on the server and creates test cases, but this becomes difficult on heavy-load production systems. Mirroring on staging platform can result in missing out on some test cases.

We are able to test changes to our APIs and make sure they are backward compatible. Issues in the response, like change in data type or addition/removal of any keys is easily captured by HyperTest.

1. Very Helpful to Generate Test Cases for Regression Testing

2. Helps Teams to capture all the APIs concerning each service for all the flows we do manually

3. Easily Helps us to find any API Failures.

4. Really Like how middleware works to randomize the data

1. UI Needs to be Improved a little bit. Sometimes the pages don't load properly

2. set up a service sometimes need other members' involvement

3. It would be very nice if we have the option to run multiple services at the same test run

1. Reducing manual effort

2. Preparing our test runs, which helps us to run whenever required

3. helps the team if any quick sanity testing is required for minor changes

Helps us with automating backend tests with ease and creating API Document.

A new platform so a lot of features are still under Beta

Automate test cases

Auto Create API documation

Hypertest unique selling point is its ability to generate tests by capturing network traffic, they have reduced the overhead of writing test cases, and its reports and integrations have helped us smoke out bugs very quickly with very little manual intervention.

The support we received from their end during the POC was excellent.

Their tool is very customizable with their Middleware integration, but documentation can be better with a few more examples.

Regression testing is one of our primary goals, most of our clients are API users, and governance is a significant factor for choosing Hypertest.

Easy to generate test cases

We would not miss any API being tested as Hypertest ensures all the requests are replayed from network traffic while running a test

This helps us in detecting any contract failures and data errors before releasing them into production

UI Is a bit overwhelming at times.

There is a dependency layer on the DevOps end for setup.

Hypertest reduces bandwidth on our team in automating test cases.

There is no need to maintain test cases as new versions are released because HyperTest automatically updates the test cases.

There is reduced effort and time in backend API testing

1. Able to achieve a good amount of automation in less time

2. No need to maintain an automated script

3. Excellent support from the Hypertest team for any queries we face while doing automation

We have already provided UI improvements, and they are working towaards it .

There is nothing to dislike about this tool

With the help of the Hypertest tool, we can automate new features while doing the first round of testing only.

We don't have to spend extra time in the sprint doing automation & helping us in releasing bug-free features to production.

I have been using Hypertest for the past 2.5 years. It has made the QA cycle reliable providing the best quality, reducing a lot of manual effort, and thus saving functional bandwidth. The bugs which can be missed in automation can be easily catch up with Hypertest.

As such no downsides, UI can be better so that it'd be easily understood to everyone. Although it has been improved in a good pace. Performance testing will be an advantage if the Hypertest team can work on this area.

1. Saving a lot of manual effort

2. Helping in debugging the issues

3. Helping in sending confident releases

4. Reducing the chances of bugs to go on production

This is very helpful in covering the API regression test cases without additional bandwidth. No coding skills needed and no extra effort require for covering new apis

Nothing as such. If we face any issues then their support helps prompty and clarify any doubts asap

Api regression testing without any manual effort

The best thing as a DevOps engineer in Hypertest I found is, that its setup is available for Kubernetes and also with steps. The documentation provided on the official site is quite comprehensive and concrete. Hypertest cli and run tests are also easy to integrate with the CICD tool. Also, the worker nodes are running on spot instances which are cost-efficient.

I am looking for the feature to get an alert on slack regarding build summary and reports.

We have achieved automated regression testing through hypertest. We are sending more efficient releases to production.