QID 580536

In this scenario exact minimum value for integer and numeric type fields, whose minimum limit is defined, are tested. For all integer and numeric type fields whose minimum is not defined, this test is skipped. Integer and numeric type fields, are replaced with exact minimum value defined in the swagger file and sent to the server for the endpoint being tested. The expectation is that APIs will accept the request as value and treat it as happy path. The purpose of the test is to verify that all defined boundaries are properly implemented. Based on testing done replacing integer and numeric values with the exact minimum defined in swagger file it is determined that the valid minimum values are accepted. The response to some valid values does not match schema definition for field being tested.

Enforcing the minimum value set on the field will help provide clarity to the API users and avoid abuse of the API by hackers. Enforcing limits help in mitigating resource exhaustion attacks. API users might be confused with the response mismatch to valid values.