Accepting Changes

1. Accepting Changes

Accept changes to confirm to HyperTest that this is a desired change so that we do not report this in future. This is the same as updating your unit tests if they fail because of an intentional code change.

1. Click on 'Accept All Changes' when you see a failed request

1. Once this is done, you will get a prompt confirming if you want to accept these changes or undo this operation.

1. If you want to move ahead, click on 'Confirm & Submit' else you can go ahead and Undo these changes.

This feature is particularly useful when you want to accept your results, be it a 'Mock Not Found' or 'AI Matched' result, and just merge your changes to your main branch.

Note: Accepting all changes for any test means that a user is forcefully making sure that the following test has passed. It will go straight to the 'passed' section of the test.

2. Bulk Accepting Changes

Like accepting intended code changes for one particular API, you can also filter the test cases based on certain difference criteria's and accept changes in Bulk. First you've to enable the bulk actions like this:

Then click on filters to select the particular difference for which you want to bulk accept changes:

Then click on Accept Changes to update these test cases:

This tells us that accept changes job completed successfully:

3. Mark as Noise

Mark those changes as Noise where an output value gets changed quite often and this change is not related to any regression in your code. For e.g. time stamp changes, geographical values(latitude & longitude), etc. from a geolocation application can give different values for same inputs. We try to detect frequently changing values on our own, but in certain scenarios we might not be able to detect it e.g., a timestamp resolution that changes every mins/hours.

We encourage you to write rules to ignore these fields for reporting of difference, you can checkout its documentation here. This is because we would like to keep the accumulating test data minimal which could affect the test run performance. Use of this feature is encouraged for rare scenarios where same issue is not observed in other APIs/Tests.

You just need to:

1. Click on the error and select 'Mark as Noise'.

2. Click on 'Accept all Changes'

This will help HyperTest identify that these changes are noise and it will not report them as error in future.