DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run PACT conformance tests against a Provider with Openpactprotocol

Check that a Provider's endpoints follow the PACT spec using the bundled e2e suite.

Authorization notice. Openpactprotocol is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA Provider engineer who has built or is building support agents for Brands and needs proof the endpoints match the protocol before going live.

The problemInterop breaks when a Provider reads Agent Cards, signed requests, or consent claims slightly differently from the spec.

The outcomeA pass or fail result from the conformance suite for the target Provider, with failing checks identified.

What you need first

  • Node.js and pnpm installed
  • Git access to clone openpactprotocol/openpactprotocol
  • PostgreSQL for the reference Provider, as named in the README
  • Basic familiarity with TypeScript and OAuth concepts

Steps

  1. Clone the repository and open its folder.
  2. Run pnpm install && pnpm gen-keys.
  3. Follow Run the reference stack in docs/running.md to start the reference Provider locally.
  4. Run the conformance suite in e2e/ with E2E_PROVIDER=any pnpm test after setting E2E_PROVIDER to your Provider's base URL. (inferred, check the README)
  5. Read the failing test names and map each one to the matching section of docs/spec.md.

Prompt for your agent

Using the openpactprotocol/openpactprotocol repo, set up the e2e conformance suite and run it against the Provider at <provider-url>. Output a list of passed and failed checks with the spec section for each failure. Verify that the suite ran against <provider-url> and not the reference Provider by checking the target in the test output.

Caveat. The README says the e2e suite runs against any Provider with E2E_PROVIDER=any, but the exact test command is not shown, so confirm it in the e2e folder before relying on it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page