Hi, I'm doing bi-directional contract testing between

PortalUI

&

ProfileService

. I have the OpenAPI specification for

PortalService

, which includes the following endpoints: • GET /profiles - return 200 or 401 • GET /profiles/{id} - return 200 or 400 or 404 or 401 They are both set to use JWT authentication. For the consumer contract, I'm running the tests shown in the screenshot (I have also attached the generated pact). On contract comparison, I get a few errors. For both endpoints I get one about

Request Authorization header is missing but is required by spec file

. It is true that the Authorization header is required, but I also want to ensure not specifying it returns a 401. This example on StackOverflow shows how to make security optional in the OpenAPI spec, but that might lead to the API implementation lacking proper security of endpoints (and a tool such as Dredd would likely not catch that, since the spec says it's optional). Any idea how to deal with this issue? For

get /profiles

I get additional

Response Body is Incompatible

errors: • Response body is incompatible with the response body schema in the spec file: should be array • Response body is incompatible with the response body schema in the spec file: should NOT have additional properties - content • Response body is incompatible with the response body schema in the spec file: should NOT have additional properties - contentType • Response body is incompatible with the response body schema in the spec file: should NOT have additional properties - encoded The

response

in the contract looks like this:

"response": {
  "body": {
    "content": [],
    "contentType": "application/json",
    "encoded": false
  },
  "headers": {
    "Content-Type": [
      "application/json; charset=utf-8"
    ]
  },
  "status": 200
}

Response body is incompatible with the response body schema in the spec file: should NOT have additional properties - encoded

Mismatched Pact Path:

[root].interactions[1].response.body

Mismatched Provider Path:

[root].paths./profiles.get.responses.200.content.application/json; charset=utf-8.schema.additionalProperties

Initially I had

additionalProperties

set to

false

in the schema for

Profile

, but even after removing that, deleting the pacts & re-publishing, it still points to that under `Mismatched Provider Path`:

Profile:
  type: object
  required:
    - id
    - username
    - picture
  additionalProperties: false
  properties:
    id:
      type: string
    username:
      type: string
    picture:
      type: string

Please post this in #pactflow

Tim’s right, if you could for next time that would be great

thanks guys! sorry I didn't realize this was just pactflow specific .. will do a better assessment next time 👍

No probs - easy to do!

No worries at all!