Forum Discussion

Powerbook14's avatar
Powerbook14
Visitor
3 years ago

Swagger Compliance Assertion is not functional

Swagger Compliance Assertion is not functional

ReadyAPI : 3.41.1

 

We have imported a Swagger 2.0 Json file in ReadyAPI.

In the Swagger Json file, the “/login” verb consume and produce “application/vnd.dcp-v1+json”.

 

TestCase 1 : Nominal test case with « /login » resource.

On this nominal test case, we use “/login” with right parameters, response body is “good” (token provided).
Returned Content-type is “application/vnd.dcp-v1+json” as expected -> OK.

 

Issue : Swagger Compliance Assertion is FAIL ?! Reason : Invalid content type [application/vnd.dcp-v1+json] -> KO

 

Test Case 2 : Error test case with “/login” resource.

In this error case, API provider makes a mistake, returned content-type is wrong, api respond with content-type = application/json, whereas “application/vnd.dcp-v1+json” is expected .

For memory, there no "application/json" in “consume” or “produce” media-type in json definition file.

Issue : Swagger Compliance Assertion is PASS ?! -> KO

 

Conclusion:

Swagger Compliance Assertion engine doesn't seem to use the provided definition file for response content-type check : it expects an "application/json" content-type anyway.

Swagger Compliance Assertion is not functional.

 

Please check pdf document in attachment (with screenshot).

 

How to open a ReadyApi issue ?

 

Thank you.

Regards,