api-pact-generate

To generate Pact consumer-driven contract tests from pinky-promise specs, run the generate command in your project directory. The tool reads specs from the registry or local draft files and outputs generated interactions as JSON alongside Pact Go test code without reading service implementations.

Yes, you can set up provider verification for Pact contract tests using pinky-promise specs. The generation process supports both Consumer and Provider roles, producing the necessary Go test code using pact-go to verify that provider services remain in sync with consumer expectations.

No, this Pact test generation tool does not read service implementations. It strictly reads API specifications from the pinky-promise registry or local draft files to automatically generate contract tests, ensuring consumer and provider services remain in sync without coupling to implementation code.

The best way to output generated Pact interactions to a broker in a Go project is by using the tool's optional publish feature. It outputs generated interactions as JSON, writes Pact Go test code to a designated directory, and can optionally publish verifications directly to a Pact broker.

Yes, you need pinky-promise specs to generate consumer-driven contract tests with pact-go using this tool. The generation process relies on reading these specs from the registry or local draft files to produce the Go test code and JSON interactions required for contract testing.

Generating Pact contract tests automatically from specs ensures consumer and provider services remain in sync without manual coding errors. It reads pinky-promise specs to output JSON interactions and pact-go test code, streamlining the creation of consumer-driven contract tests.