@Gazal Gafoor has left the channel

@Facu Conejero has left the channel

@Kripa Kurian has left the channel

Can I disable the verification results requirement?

We are doing a pactflow POC, and I’d like to get a sanity check on what we’re attempting… we’d like to pilot bidirectional contract testing, and our services communicate via async messaging over (pulsar) queues.

Hi , I am looking to do a POC for contract testing with pact on a Frontend (Legacy Python Pyramid app: consumer) and a microservice (Python API). Because both consumer and provider are legacy apps, its not easy to bring them up locally to be able to perform consumer driven contract testing. So i read about Bi-directional contract testing where I can use the exisiting OpenAPi spec and a testing tool in provider side to create a contract and still implement contract testing workflow . I still just want to ask this question to this group to validate if this is the path i can take forward or am i missing something here ? Appreciate your help

Hi all, anyway we can turn off the header warnings?

Hi All, I have a question about testing message based systems: with http consumer based testing, you start the provider service and have the ability to set state. With a message based system, is there still the ability to run the provider and set up state? All of the examples I’ve seen look like straight unit tests that don’t involve running the provider. I’m wondering if I’m missing something. Thanks!

Hey all, we have this validation error, however all the validators were running against say the OAS is valid.. How is this being determine / How can we perform this check locally to find the issue?

"nullable" cannot be used without "type"

@Amit Wertheimer has left the channel

Hello) My company uses PactFlow and now we're exploring bi-directional tests. Microservices of our product may have multiple API versions and in this case multiple OAS files are generated (we use Swagger). Can PactFlow somehow handle different API versions of Provider if they are stored in separate docs? I tried uploading them one at a time, but they override each other. Thank you in advance.

@Tõnis Ojandu has left the channel

Am I correct in that generating the provider-side contract in PactFlow is limited to the following two options? 1. Upload OpenAPI (OAS), which contains only schema information and decoupled examples of possible inputs and outputs? 2. Running the Consumer's pact against a running instance of the Provider (and therefore all of its dependencies as well).

Hi Team, we are trying to achieve a bidirectional approach for messaging pacts, does pactflow support messaging based system specification file?

Hi all, Is there an option to integrate pactflow with slack to get notification on slack channel whenever new contract is published?

Has anyone did any research around this topic?

A dumb question may be : we are trying to help a client implement contract testing and they have thrift protocol between services is what I understand. Can somebody please explain the relevance of contract testing in such a situation? @Yousaf Nabi (pactflow.io) @Matt (pactflow.io / pact-js / pact-go)

Hey all, small question, but our provider contracts have an issue per pactflow:

Cannot read properties of undefined (reading 'type')

but thats all we get for the error message. Does any stacktrace or line number exist for this error? Having trouble going though the provider contract to find the issue.

@Ruth has left the channel

@Cody Jenkins has left the channel

👋 I need to establish a conformance certification program around an OAS that will have three conformance profiles related to three subsets of the overall OAS (forecast, real-time, and peering). I need to be able to certify conformance of multiple implementations of the OAS, and I'd like to be able to provide the conformance test suite to implementors for their use in their own CI/CD pipelines. (Part of the conformance suite will be a data file that represents that provider state at the beginning of the test.) I don't have a mandate to build clients or a provider, but I think I will need to build at least the latter of those to develop the conformance profile tests. Each of the profiles will need to ensure the successful execution of a handful of scenarios. A primary consideration is the DevEx of the provider implementors. In particular, I want it to be easy for them to understand why a particular scenario is not passing; some scenarios may involve a series of API calls so being able grok the overall journey is important. I am also concerned about sustainment: HTTP, JSON, and OAS were safe, accessible choices with long-term ecosystems. Relatedly, I need something that is "free-as-in-beer", even if the project is ultimately able to fund some quality of life improvements in the toolchain. There's more than one way to do it, as they say. I've looked at Karate, Hoppscotch, Postman/Newman, and Insomnia/Inso. They all seem plausible. My gut tells me that I want the provider contracts to live as independent artifacts of equal importance alongside the OAS itself. More to the point, since the OAS was developed spec-first instead of TDD/BDD-style, I'm quite certain developing the provider contract will identify gaps and other failings in the design, so I'd like to iterate the OAS and the contracts together until 1.0. Would you have any advice to give?

Hi all Is verification of XML responses in the roadmap? If not is there a way for us to build that feature ?

@Alejandro Sanchez Giraldo has left the channel

@Evan Rademacher has left the channel

@Taha Shakibania has left the channel

@PK has left the channel

Hello people, My project uses FastAPI and OpenAPI schemas. Can someone recommend what library or libraries I should use with these? Any leads are highly appreciated.

Hi, I wanted to ask if it would somehow affect the licensing terms and how you would feel if I made a public repo(fork) where the following GitHub actions work with the OSS PactBroker (no need to use PactFlow) https://github.com/pactflow/actions I understand it's an unusual question, but I wouldn't want to proceed in conflict with the PactFlow org.

@Diego Betancur has left the channel

Hi all I am experiencing an issue with

discriminator

I have the following example schema:

components:
  schema:
    full-request:
      title: Full request
      description: This is the full request
      type: object
      properties:
        type:
          description: Type of request
          type: string
        payload:
          description: Request payload
          type: object
          oneOf:
            - $ref: '#/components/schemas/ORIGIN_A'
            - $ref: '#/components/schemas/ORIGIN_B'
          discriminator:
            propertyName: originator
      required:
        - type
        - payload
    ORIGIN_A:
      type: object
      schema:
        allOf:
          - $ref: '#/components/schemas/common'
          - type: object
            properties:
              originator:
                const: ORIGIN_A
              originatorId:
                $ref: '#/components/schemas/origin-id'
            required:
              - originator
              - originatorId
    ORIGIN_B:
      type: object
      schema:
        allOf:
          - $ref: '#/components/schemas/common'
          - type: object
            properties:
              originator:
                const: ORIGIN_B
            required:
              - originator

Pactflow is not able to handle the discriminator in this case, I get the following message:

discriminator: oneOf subschemas (or referenced schemas) must have "properties/originator"

Looking through the docs I can't understand why that isn't working.