NOTE: This library is being moved into a single FFI library pact_ffi.
This library implements exported functions using C bindings for controlling the in-process mock server for matching HTTP requests and generating responses from a pact file.
Includes all the FFI functions from the
Initialise the mock server library, can provide an environment variable name to use to set the log levels.
External interface to create a mock server. A pointer to the pact JSON as a C string is passed in, as well as the port for the mock server to run on. A value of 0 for the port will result in a port being allocated by the operating system. The port of the mock server is returned.
External interface to create a mock server. A Pact handle is passed in, as well as the port for the mock server to run on. A value of 0 for the port will result in a port being allocated by the operating system. The port of the mock server is returned.
Simple function that returns a boolean value given the port number of the mock service. This value will be true if all the expectations of the pact that the mock server was created with have been met. It will return false if any request did not match, an un-recognised request was received or an expected request was not received.
This returns all the mismatches, un-expected requests and missing requests in JSON format, given the port number of the mock server.
IMPORTANT NOTE: The JSON string for the result is allocated on the rust heap, and will have to be freed once the
code using the mock server is complete. The
cleanup_mock_server function is provided for this purpose. If the mock
server is not cleaned up properly, this will result in memory leaks as the rust heap will not be reclaimed.
This function will try terminate the mock server with the given port number and cleanup any memory allocated for it by
mock_server_mismatches function. Returns
true, unless a mock server with the given port number does not exist,
or the function fails in some way.
close() on the listener for the mock server is called, this does not currently work and the
listerner will continue handling requests. In this case, it will always return a 501 once the mock server has been
External interface to trigger a mock server to write out its pact file. This function should be called if all the consumer tests have passed. The directory to write the file to is passed as the second parameter. If a NULL pointer is passed, the current working directory is used.
Returns 0 if the pact file was successfully written. Returns a positive code if the file can not be written, or there is no mock server running on that port or the function panics.
For languages that need to build up Pact models, there are two structs that represent a handle to a Pact model (PactHandle and InteractionHandle). These handles will refer to Rust Pact models stored on the rust heap.
To create a new Pact model, use new_pact and then you can use the following DSL support functions to build up the model.
Creates a new Interaction and returns a handle to it.
Sets the description for the Interaction.
Adds a provider state to the Interaction.
Configures the request method and path for the Interaction.
Configures a query parameter for the Interaction.
Configures a header for the Interaction.
Configures the response for the Interaction.
Adds the body for the interaction.