Skip to content
This repository has been archived by the owner on May 15, 2023. It is now read-only.

Access to response for custom assertion #162

Open
xke7 opened this issue Nov 9, 2017 · 1 comment
Open

Access to response for custom assertion #162

xke7 opened this issue Nov 9, 2017 · 1 comment

Comments

@xke7
Copy link

xke7 commented Nov 9, 2017

It could be good to define additional assertion while generating tests

@biancajiang
Copy link

biancajiang commented Nov 10, 2017

+1

Similar to "requestData", ability to have "expectedResponse" or "expectedData" for each input (from requestData) will be very valuable. Basic assertion like assert.deepEqual() for json responses.

Can be as simple as:

{
   '/pet': {
       get: {
           '200': [
               { param: 'spot', description:'some description of the data', expected: expectedJSONresponeForSpot},
               { param: 'tops', description:'some description of the data', expected: expectedJSONresponeForTops}
            ]
       }
   }
 }

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants