CodeVetter · Repo Unpack · Behavior traces
pact-foundation/pact-js
Three concrete flows were followed through source: V4 HTTP consumer testing, HTTP provider verification, and V4 asynchronous message testing. Each trace follows declaration, execution, and persistence or result handling. The examples show application clients and handlers participating in those flows rather than treating the library's builders as the entire test.
- HTTP consumer startup: new Pact constructs PactV4 → setup → makeConsumerPact with default V4 → addMetadata; addInteraction then creates a native interaction and an UnconfiguredInteraction carrying a parent-reset callback.
- HTTP declaration: given/uponReceiving configure native state and description → withRequest configures method/path and runs RequestBuilder → willRespondWith sets status and runs ResponseBuilder → returns InteractionWithResponse.
- HTTP execution: InteractionWithResponse.executeTest → shared executeTest → native transport mock startup → UserServiceClient.getUser sends Axios GET → callback assertions → mismatch checks → writePactFile/cleanup/reset; callback errors are rethrown and failure branches skip writing.
- Provider startup: the example starts createApp on port 3001 → constructs Verifier with the generated pact path and state handlers → verifyProvider creates hooks state and proxy → waitForServerReady → runProviderVerification → verifyPacts.
- Provider state and request replay: /_pactSetup runs hook middleware before requestFilter and state dispatch → setupStates invokes the named callback → clearUsers/seedUser populate the example Map → other requests reach proxy.web → createApp returns /users or /users/:id JSON.
- Provider completion: registerHooks records hook exceptions while continuing middleware; after verifyPacts resolves, verifyProvider closes the server and rejects recorded hook errors, and its catch branch also closes the server before rethrowing.
- Async message declaration: PactV4.addAsynchronousInteraction → newAsynchronousMessage → given → expectsToReceive → AsynchronousMessageBuilder.withJSONContent/withMetadata; the OrderPlaced example supplies matching declarations and queue metadata.
- Async execution and persistence: AsynchronousMessageWithContent.executeTest → executeNonTransportTest → reifyMessage/JSON.parse → v4SynchronousBodyHandler extracts contents.content → application handler; callback failure cleans without writing, while success writes ./pacts or opts.dir, cleans plugins, and resets.