Understanding Results Categories

1. Passed Requests

These requests will have no regressions in the responses or their outbound calls.

In this example, the response of the request or it's outbound calls show no regression.

2. Failed Requests

Requests with regressions in responses or any of its outbound calls.

2.1 Understanding a failed request

Check any failed requests to understand what Hypertest reports. It asserts for response codes, schema and data across responses and outbound call. See the example below of a data regression

1. This is an example of Value Modified, in the path, 'newBalance'.

2. Why did Hypertest report this problem. When the API works fine, the field newBalance gets correctly updated when someone adds $500, as seen in Expected Response. However, when the code was updated it caused an error making it debit instead of credit the same amount. When HyperTest ran the request with the same data set it caught the difference you see in newBalance.

3. We can magnify the scope of our investigation by looking at the JSON View, which tells us the actual difference in the form of a JSON file.

2.2 Checking the Outbound call responsible

HyperTest can similarly assert the schema and data in outbound calls.

In the same example, once the NewBalance is computed the service updates it to a database like PostgreSQL here. HyperTest asserts for schema and data in the db query like it did for API response above and reports a regression like you see above.