A way to test 422 response or to avoid automatic testing of this response

[oliviernguyenquoc]

Hi,

I have 2 type of response written in my OpenAPI.yaml file for a route:
First, the "OK" response, a 201 code response.
Second, the "Not OK" response, a 422 code response

   post:
      requestBody:
        description: Brand to create
        content:
          application/json:
            schema:
              $ref: "#/components/schemas/Foo"
            examples:
              ...
        required: true
      responses:
        "201":
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Bar"
              examples:
                ....
          description: Successful Response
        "422":
          description: Validation Error
          content:
            application/json: 
               ...

So I have 2 questions:
1/ Is it possible to have a different requestBody to test both "OK" (Code: 201) scenario and "Not OK" (Code 422) scenario ?
2/ If not, how to tell microcks to avoid to test this response, during contract testing ?

[lbroudoux]

Hi @oliviernguyenquoc,

1/ Is it possible to have a different requestBody to test both "OK" (Code: 201) scenario and "Not OK" (Code 422) scenario ?

Yes definitely! You can define different fragments that will be merged together. Something like:

   post:
      requestBody:
        description: Brand to create
        content:
          application/json:
            schema:
              $ref: "#/components/schemas/Foo"
            examples:
              expect_201:
                value: 
                   ...
              expect_422:
                value: 
                   ...
        required: true
      responses:
        "201":
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Bar"
              examples:
                expect_201:
                value: 
                   ...
          description: Successful Response
        "422":
          description: Validation Error
          content:
            application/json: 
              examples:
                expect_422:
                  value: 
                    ...

In mocking mode, the 2 request/response pairs will give you the different response codes 201 and 422.

In testing mode, the 2 requests will be issued to endpoint and expect the 2 different response codes 201 and 422.