fix: schema validation and ajv not working

[jarlah]

I encountered an issue where missing required fields did not cause test failures. I therefore debugged the contract generator and found ajv was used in a wrong way. https://ajv.js.org shows the usage I have changed it to

[jarlah]

plus, I moved console log of errors above pm expect since it doesn't continue if it fails

[jarlah]

This is actually a pretty hard bug to spot, if you dont force tests to fail by changing openapi spec to include required schema fields that are not present in response json.

Can you look at this @allenheltondev ?

[jarlah]

im unsure if the block above that checks ref is correct, because I have only responses with schema in my spec. But should we change that too? or is it correct, based on the fact that it doesn't compile and just runs validate directly ? maybe some differences in usage in ajv ?

[jarlah]

this is the code im talking about which also might need changes

https://github.com/allenheltondev/postman-contract-test-generator/pull/20/files#diff-9e956785d7866429945ba214628c271f4c96863c8fcd2a6c8d69c380804ab9c9R1307

[jarlah]

not able to force the if statement for expectedResponse.$ref to be true. Even when I set

responses:
    "200":
      $ref: '../responses/MyResponse.yaml'

it has a schema still. The schema of MyResponse. So maybe the first can be removed ?

I see in should shouldResponseBeEmpty that there is a check against #/components/responses if $ref attribute exists .. but my approach of splitting up the yaml files work pretty ok with postman and all other openapi tools. Even if I use relative paths in the project with the openapi spec, its converted to #/components/ references when I export the openapi spec from the tool that imported it