Hi RobWin,
This PR is about enabling a configuration validateResponseWithStrictlyMatch to allow loosely match for actual swagger response to expected swagger response.
The reason I added this is, I am working on a project which migrates an old API to a new one. We need all the old API compatible with new API (subset of the new one).
Coverage increased (+0.7%) to 90.154% when pulling 311a36aafd01cca41dfc8c84fa3994e72a43e01b on zacyang:master into ba1594c73717efdce9548359eb6f19beb1512eb3 on RobWin:master.
Hi RobWin, This PR is about enabling a configuration
validateResponseWithStrictlyMatch
to allow loosely match for actual swagger response to expected swagger response.The reason I added this is, I am working on a project which migrates an old API to a new one. We need all the old API compatible with new API (subset of the new one).
Could you please accept this PR. Thanks.