Skip to main content

Strategies for verifying feature pacts

When a new "feature" pact is created, there are a few ways you could bring that pact into the verification process so that the verification results get published back to Pactflow from your CI.

  1. Manually add the feature tag to the consumerVersionSelectors, commit it, and then remove it once the feature is released.

    consumerVersionSelectors: [    { tag: 'master', latest: true },    { tag: 'feat/new-field', latest: true },    ...]
    • This does the job, but it's a bit fiddly, and there are better options.
  2. Make a matching feature branch in the provider, and dynamically fetch the pact for the matching consumer branch if it exists (no error will be raised if a pact does not exist for a particular tag). This is a reasonably common approach, where the two teams coordinate feature development using matching branch names.

    consumerVersionSelectors: [    { tag: 'master', latest: true },    { tag: process.env.GIT_BRANCH, latest: true },    ...]
  3. Enable "work in progress" pacts.

Work In Progress Pacts#

The "work in progress pacts" feature solves the problem of provider teams having to manually update and commit changes to their verification configuration to publish verifications for feature pacts from CI.

When enabled, it will cause the provider to automatically verify, in pending mode, any "outstanding" pacts (ie. ones for which it has not yet published a successful result), as well as the pacts that were explicitly specified in the tag/selector list.

A "work in progress" pact is a pact that is the latest for its tag that does not have any successful verification results (ie. is still pending) for the configured provider tag . At this stage in the exercise, the feat/new-field pact is still in pending state for the master branch of the provider, so it is considered a "work in progress" pact for master.

The verification task can be configured to automatically include work in progress pacts, so that the consumer team can get feedback on their changed pacts without having to wait on action from the provider team.

๐Ÿ‘‰ Something that is important to understand about the calculation of the WIP pacts list is that it is calculated based on the tag that will be applied to the provider version. For example, if a pact only has a successful verification from a provider version with tag feat/x, it will still be pending for a provider version with tag master (and every other tag).

The reason for this is that if support for a new feature pact is added on a feat/x branch of the provider, you still want to keep getting the failed verification results from master until the feat/x branch is merged.

Enable Work In Progress Pacts for the provider#

  1. In the provider project, open src/product/product.pact.test.js and in the options for the dynamically fetched pacts, set includeWipPactsSince: "2020-01-01"

  2. Run GIT_BRANCH=master make test and you will see that the feat/new-field pact has been included in the verifications, running in pending mode.

    • We need to set the GIT_BRANCH when running locally so that the WIP calculations know which pending pacts to include.
  3. Commit and push

  4. Open the provider build in Github Actions and wait for the successful verification result for feat/new-field to be be published.

    • ๐Ÿ‘‰ Note that the provider has now successfully deployed this change to production, so the consumer is now free to release their code.
  5. On your local machine, run GIT_BRANCH=master make test - you will now see that the feat/new-field pact is not included, as it is no longer a work in progress pact.

Expected state by the end of this step#

  • A feat/new-field pact in Pactflow that has successful verification results from a version of the provider that has both master and prod tags.

Conclusion#

Enabling 'work in progress' pacts allows the consumer to get feedback on a changed pact without the provider having to make configuration changes on their end.

If the verification for the changed pact passes without the provider having to make any changes to the code, then the consumer is free to release their feature, without making the provider a bottleneck.