QID 580518

In this scenario maximum value for integer type fields, whose maximum limit is defined, are tested. This test is skipped for all integer fields where maximum value is not defined. For each integer field, on end points being tested, values more than the maximum defined in the swagger file are sent to the server. The expectation is that APIs will reject the request as invalid, if the value is more than it's maximum. The response from server for requests with integer value more than maximum allowed should match the schema definition for invalid request.

Based on reviewing responses for requests with values higher than the maximum defined in the swagger file it is determined that the maximum values defined for integer fields are enforced but not as expected. The request with invalid values is rejected. The response code received for the request with higher values for integer fields is expected but the response does not match the response documented in the swagger file schema.

Enforcing the maximum value set on the field will help provide clarity to the API users and avoid abuse of the API by hackers. Since the response does not match the swagger documentation of the end point API users do not have clarity.