Example .NET Consumer - WireMock.Net

• Example .NET Consumer - WireMock.Net
  • Overview of Example
  • Overview of Part of Bi-Directional Contract Testing Flow
  • Compatibile with Providers
  • Pre-requisites
    • Environment variables
  • Usage
    • Steps
  • OS/Platform specific considerations
    • Windows
  • Caveats
  • Related topics / posts / discussions
  • Found an issue?

Overview of Example

This is an example of a .NET "Product" API consumer that uses WireMock.Net, PactFlow and GitHub Actions to generate and publish Pact consumer contracts.

It performs pre-deployment cross-compatibility checks to ensure that it is compatible with specified providers using the Bi-Directional contract capability of PactFlow.

See the full PactFlow Bi-Directional Workshop for which this can be substituted in as the "consumer".

Overview of Part of Bi-Directional Contract Testing Flow

In the following diagram, You can see how the consumer testing process works - it's the same as the current Pact process.

When we call "can-i-deploy" the cross-contract validation process kicks off on PactFlow, to ensure any consumer consumes a valid subset of the OAS for the provider.

The project uses a Makefile to simulate a very simple build pipeline with two stages - test and deploy.

When you run the CI pipeline (see below for doing this), the pipeline should perform the following activities (simplified):

• Test
  • Run tests (including the pact tests that generate the contract)
  • Publish pacts, tagging the consumer version with the name of the current branch
  • Check if we are safe to deploy to Production with can-i-deploy (ie. has the cross-contract validation has been successfully performed)
• Deploy (only from main)
  • Deploy app to Production
  • Record the Production deployment in the Pact Broker

Compatibile with Providers

This project is currently compatible with the following provider(s):

• pactflow-example-bi-directional-provider-dotnet

See Environment variables on how to set these up.

Pre-requisites

Software:

• Tools listed at: https://docs.pactflow.io/docs/workshops/ci-cd/set-up-ci/prerequisites/
• A pactflow.io account with an valid API token

• .NET core 8.x SDK installed, this is the version of .NET core used for this example.
• Docker running on your local machine

Environment variables

To be able to run some of the commands locally, you will need to export the following environment variables into your shell:

• PACT_BROKER_TOKEN: a valid API token for PactFlow
• PACT_BROKER_BASE_URL: a fully qualified domain name with protocol to your pact broker e.g. https://testdemo.pactflow.io

Set PACT_PROVIDER to one of the following

• PACT_PROVIDER=pactflow-example-bi-directional-provider-dotnet: SchemaThesis - (https://github.com/pactflow/example-bi-directional-provider-dotnet)

Usage

Steps

• make test - run the tests locally
• make fake_ci - run the CI process, but locally

OS/Platform specific considerations

The makefile is configured to run on Unix based systems such as you would find in most common CI/CD pipelines.

They can be run locally on Unix/Mac, or on Windows via WSL2.

Windows

You can still try this example locally on Windows using powershell and running commands manually.

Click to see windows specific instructions here

1. Make sure you have set all of the environment variables, in powershell they can be set like so.

    $env:GIT_BRANCH="main"
   

2. Generate the Pact file for the example by opening the solution and running the tests in visual studio, or using dotnet test CLI command in the root directory of the project.

3. Publish the pact that was generated. The step uses the pact-cli docker image to publish the pact to your pactflow account. The path for <path_to_project_root> needs to be converted from Windows paths to UNIX ones as the Docker container is using UNIX. Either hard code this or set it as another environment variable.

   `C:\Users\Person\Documents\example-bi-directional-consumer-wiremock-dotnet`
   
   becomes
   
   `/c/Users/Candy/Documents/Pactflow/example-bi-directional-consumer-wiremock-dotnet`
   
   $env:VARIABLE_NAME refers to the environment variables in windows.
   
   ```
   docker run --rm -v <path_to_project_root>:<path_to_project_root> -e PACT_BROKER_BASE_URL -e PACT_BROKER_TOKEN pactfoundation/pact-cli publish <path_to_pacts_folder> --consumer-app-version $env:GIT_COMMIT --tag $env:GIT_BRANCH
   
   ```
   

4. Check can-i-deploy to see if your provider is compatible with your pact.

   docker run --rm -v <path_to_project_root>:<path_to_project_root> -e PACT_BROKER_BASE_URL -e PACT_BROKER_TOKEN pactfoundation/pact-cli  broker can-i-deploy --pacticipant pactflow-example-bi-directional-consumer-wiremock-dotnet --version $env:GIT_COMMIT --to-environment production  --retry-while-unknown 0 --retry-interval 10
   

5. Have a look at what other commands are available in the Makefile. All of them can be ran locally from Powershell by changing the windows paths to UNIX and replacing the environment variable references. Any variable referenced as ${VARIABLE} can be changed to $env:VARIABLE to reference environment variables in Powershell.

Caveats

• OAS considerations

Related topics / posts / discussions

• Consumer Side Bi-Directional Contract Testing Guide
• Provider Side Bi-Directional Contract Testing Guide

Found an issue?

Reach out via a GitHub Issue, or reach us over in the Pact foundation Slack