Skip to main content

pact-jvm-consumer-junit

Provides a DSL and a base test class for use with Junit to build consumer tests.

Dependency​

The library is available on maven central using:

  • group-id = au.com.dius.pact.consumer
  • artifact-id = junit
  • version-id = 4.2.9

Usage​

Using the base ConsumerPactTest​

To write a pact spec extend ConsumerPactTest. This base class defines the following four methods which must be overridden in your test class.

  • providerName: Returns the name of the API provider that Pact will mock
  • consumerName: Returns the name of the API consumer that we are testing.
  • createFragment: Returns the PactFragment containing the interactions that the test setup using the ConsumerPactBuilder DSL
  • runTest: The actual test run. It receives the URL to the mock server as a parameter.

Here is an example:

import au.com.dius.pact.consumer.dsl.PactDslWithProvider;
import au.com.dius.pact.consumer.junit.exampleclients.ConsumerClient;
import au.com.dius.pact.consumer.ConsumerPactTest;
import au.com.dius.pact.model.PactFragment;
import org.junit.Assert;

import java.io.IOException;
import java.util.HashMap;
import java.util.Map;

import static org.junit.Assert.assertEquals;

public class ExampleJavaConsumerPactTest extends ConsumerPactTest {

    @Override
    protected RequestResponsePact createFragment(PactDslWithProvider builder) {
        Map<String, String> headers = new HashMap<String, String>();
        headers.put("testreqheader", "testreqheadervalue");

        return builder
            .given("test state") // NOTE: Using provider states are optional, you can leave it out
            .uponReceiving("ExampleJavaConsumerPactTest test interaction")
                .path("/")
                .method("GET")
                .headers(headers)
            .willRespondWith()
                .status(200)
                .headers(headers)
                .body("{\"responsetest\": true, \"name\": \"harry\"}")
            .given("test state 2") // NOTE: Using provider states are optional, you can leave it out
            .uponReceiving("ExampleJavaConsumerPactTest second test interaction")
                .method("OPTIONS")
                .headers(headers)
                .path("/second")
                .body("")
            .willRespondWith()
                .status(200)
                .headers(headers)
                .body("")
            .toPact();
    }


    @Override
    protected String providerName() {
        return "test_provider";
    }

    @Override
    protected String consumerName() {
        return "test_consumer";
    }

    @Override
    protected void runTest(MockServer mockServer, PactTestExecutionContext context) throws IOException {
        Assert.assertEquals(new ConsumerClient(mockServer.getUrl()).options("/second"), 200);
        Map expectedResponse = new HashMap();
        expectedResponse.put("responsetest", true);
        expectedResponse.put("name", "harry");
        assertEquals(new ConsumerClient(mockServer.getUrl()).getAsMap("/", ""), expectedResponse);
        assertEquals(new ConsumerClient(mockServer.getUrl()).options("/second"), 200);
    }
}

Using the Pact JUnit Rule​

Thanks to @warmuuh we have a JUnit rule that simplifies running Pact consumer tests. To use it, create a test class and then add the rule:

1. Add the Pact Rule to your test class to represent your provider.​

    @Rule
    public PactProviderRule mockProvider = new PactProviderRule("test_provider", "localhost", 8080, this);

The hostname and port are optional. If left out, it will default to 127.0.0.1 and a random available port. You can get the URL and port from the pact provider rule.

2. Annotate a method with Pact that returns a pact fragment for the provider and consumer​

    @Pact(provider="test_provider", consumer="test_consumer")
    public RequestResponsePact createPact(PactDslWithProvider builder) {
        return builder
            .given("test state")
            .uponReceiving("ExampleJavaConsumerPactRuleTest test interaction")
                .path("/")
                .method("GET")
            .willRespondWith()
                .status(200)
                .body("{\"responsetest\": true}")
            .toPact();
    }

You can leave the provider name out. It will then use the provider name of the first mock provider found. I.e.,

    @Pact(consumer="test_consumer") // will default to the provider name from mockProvider
    public RequestResponsePact createFragment(PactDslWithProvider builder) {
        return builder
            .given("test state")
            .uponReceiving("ExampleJavaConsumerPactRuleTest test interaction")
                .path("/")
                .method("GET")
            .willRespondWith()
                .status(200)
                .body("{\"responsetest\": true}")
            .toPact();
    }

3. Annotate your test method with PactVerification to have it run in the context of the mock server setup with the appropriate pact from step 1 and 2​

    @Test
    @PactVerification("test_provider")
    public void runTest() {
        Map expectedResponse = new HashMap();
        expectedResponse.put("responsetest", true);
        assertEquals(new ConsumerClient(mockProvider.getUrl()).get("/"), expectedResponse);
    }

You can leave the provider name out. It will then use the provider name of the first mock provider found. I.e.,

    @Test
    @PactVerification
    public void runTest() {
        // This will run against mockProvider
        Map expectedResponse = new HashMap();
        expectedResponse.put("responsetest", true);
        assertEquals(new ConsumerClient("http://localhost:8080").get("/"), expectedResponse);
    }

For an example, have a look at ExampleJavaConsumerPactRuleTest

Requiring a test with multiple providers​

The Pact Rule can be used to test with multiple providers. Just add a rule to the test class for each provider, and then include all the providers required in the @PactVerification annotation. For an example, look at PactMultiProviderTest.

Note that if more than one provider fails verification for the same test, you will only receive a failure for one of them. Also, to have multiple tests in the same test class, the providers must be setup with random ports (i.e. don't specify a hostname and port). Also, if the provider name is left out of any of the annotations, the first one found will be used (which may not be the first one defined).

Requiring the mock server to run with HTTPS​

The mock server can be started running with HTTPS using a self-signed certificate instead of HTTP. To enable this set the https parameter to true.

E.g.:

    @Rule
    public PactProviderRule mockTestProvider = new PactProviderRule("test_provider", "localhost", 8443, true,
      PactSpecVersion.V2, this);                                                                     // ^^^^

For an example test doing this, see PactProviderHttpsTest.

NOTE: The provider will start handling HTTPS requests using a self-signed certificate. Most HTTP clients will not accept connections to a self-signed server as the certificate is untrusted. You may need to enable insecure HTTPS with your client for this test to work. For an example of how to enable insecure HTTPS client connections with Apache Http Client, have a look at InsecureHttpsRequest.

Requiring the mock server to run with HTTPS with a keystore​

The mock server can be started running with HTTPS using a keystore. To enable this set the https parameter to true, set the keystore path/file, and the keystore's password.

E.g.:

    @Rule
    public PactProviderRule mockTestProvider = new PactProviderRule("test_provider", "localhost", 8443, true,
            "/path/to/your/keystore.jks", "your-keystore-password", PactSpecVersion.V2, this);

For an example test doing this, see PactProviderHttpsKeystoreTest.

Setting default expected request and response values​

If you have a lot of tests that may share some values (like headers), you can setup default values that will be applied to all the expected requests and responses for the tests. To do this, you need to create a method that takes single parameter of the appropriate type (PactDslRequestWithoutPath or PactDslResponse) and annotate it with the default marker annotation (@DefaultRequestValues or @DefaultResponseValues).

For example:

    @DefaultRequestValues
    public void defaultRequestValues(PactDslRequestWithoutPath request) {
      Map<String, String> headers = new HashMap<String, String>();
      headers.put("testreqheader", "testreqheadervalue");
      request.headers(headers);
    }

    @DefaultResponseValues
    public void defaultResponseValues(PactDslResponse response) {
      Map<String, String> headers = new HashMap<String, String>();
      headers.put("testresheader", "testresheadervalue");
      response.headers(headers);
    }

For an example test that uses these, have a look at PactProviderWithMultipleFragmentsTest

Note on HTTP clients and persistent connections​

Some HTTP clients may keep the connection open, based on the live connections settings or if they use a connection cache. This could cause your tests to fail if the client you are testing lives longer than an individual test, as the mock server will be started and shutdown for each test. This will result in the HTTP client connection cache having invalid connections. For an example of this where the there was a failure for every second test, see Issue #342.

Using the Pact DSL directly​

Sometimes it is not convenient to use the ConsumerPactTest as it only allows one test per test class. The DSL can be used directly in this case.

Example:

import au.com.dius.pact.consumer.ConsumerPactBuilder;
import au.com.dius.pact.consumer.PactVerificationResult;
import au.com.dius.pact.consumer.junit.exampleclients.ProviderClient;
import au.com.dius.pact.model.MockProviderConfig;
import au.com.dius.pact.model.RequestResponsePact;
import org.junit.Test;

import java.io.IOException;
import java.util.HashMap;
import java.util.Map;

import static au.com.dius.pact.consumer.ConsumerPactRunnerKt.runConsumerTest;
import static org.junit.Assert.assertEquals;

/**
 * Sometimes it is not convenient to use the ConsumerPactTest as it only allows one test per test class.
 * The DSL can be used directly in this case.
 */
public class DirectDSLConsumerPactTest {

    @Test
    public void testPact() {
        RequestResponsePact pact = ConsumerPactBuilder
                .consumer("Some Consumer")
                .hasPactWith("Some Provider")
                .uponReceiving("a request to say Hello")
                .path("/hello")
                .method("POST")
                .body("{\"name\": \"harry\"}")
                .willRespondWith()
                .status(200)
                .body("{\"hello\": \"harry\"}")
                .toPact();

        MockProviderConfig config = MockProviderConfig.createDefault();
        PactVerificationResult result = runConsumerTest(pact, config, (mockServer, context) -> {
            Map expectedResponse = new HashMap();
            expectedResponse.put("hello", "harry");
            try {
                assertEquals(new ProviderClient(mockServer.getUrl()).hello("{\"name\": \"harry\"}"),
                        expectedResponse);
            } catch (IOException e) {
                throw new RuntimeException(e);
            }
        });

        if (result instanceof PactVerificationResult.Error) {
            throw new RuntimeException(((PactVerificationResult.Error)result).getError());
        }

        assertEquals(PactVerificationResult.Ok.INSTANCE, result);
    }

}

The Pact JUnit DSL​

The DSL has the following pattern:

.consumer("Some Consumer")
.hasPactWith("Some Provider")
.given("a certain state on the provider")
    .uponReceiving("a request for something")
        .path("/hello")
        .method("POST")
        .body("{\"name\": \"harry\"}")
    .willRespondWith()
        .status(200)
        .body("{\"hello\": \"harry\"}")
    .uponReceiving("another request for something")
        .path("/hello")
        .method("POST")
        .body("{\"name\": \"harry\"}")
    .willRespondWith()
        .status(200)
        .body("{\"hello\": \"harry\"}")
    .
    .
    .
.toPact()

You can define as many interactions as required. Each interaction starts with uponReceiving followed by willRespondWith. The test state setup with given is a mechanism to describe what the state of the provider should be in before the provider is verified. It is only recorded in the consumer tests and used by the provider verification tasks.

Building JSON bodies with PactDslJsonBody DSL​

NOTE: If you are using Java 8, there is no separate Java 8 support library anymore, there is an updated DSL for consumer tests requiring a minimum of Java 11.

The body method of the ConsumerPactBuilder can accept a PactDslJsonBody, which can construct a JSON body as well as define regex and type matchers.

For example:

PactDslJsonBody body = new PactDslJsonBody()
    .stringType("name")
    .booleanType("happy")
    .hexValue("hexCode")
    .id()
    .ipAddress("localAddress")
    .numberValue("age", 100)
    .timestamp();

DSL Matching methods​

The following matching methods are provided with the DSL. In most cases, they take an optional value parameter which will be used to generate example values (i.e. when returning a mock response). If no example value is given a random one will be generated.

methoddescription
string, stringValueMatch a string value (using string equality)
number, numberValueMatch a number value (using Number.equals)*
booleanValueMatch a boolean value (using equality)
stringTypeWill match all Strings
numberTypeWill match all numbers*
integerTypeWill match all numbers that are integers (both ints and longs)*
decimalTypeWill match all real numbers (floating point and decimal)*
booleanTypeWill match all boolean values (true and false)
stringMatcherWill match strings using the provided regular expression
timestampWill match string containing timestamps. If a timestamp format is not given, will match an ISO timestamp format
dateWill match string containing dates. If a date format is not given, will match an ISO date format
timeWill match string containing times. If a time format is not given, will match an ISO time format
ipAddressWill match string containing IP4 formatted address.
idWill match all numbers by type
hexValueWill match all hexadecimal encoded strings
uuidWill match strings containing UUIDs
includesStrWill match strings containing the provided string
equalsToWill match using equals
matchUrlDefines a matcher for URLs, given the base URL path and a sequence of path fragments. The path fragments could be strings or regular expression matchers
nullValueMatches the JSON Null value

* Note: JSON only supports double precision floating point values. Depending on the language implementation, they may be parsed as integer, floating point or decimal numbers.

Ensuring all items in a list match an example​

Lots of the time you might not know the number of items that will be in a list, but you want to ensure that the list has a minimum or maximum size and that each item in the list matches a given example. You can do this with the arrayLike, minArrayLike and maxArrayLike functions.

functiondescription
eachLikeEnsure that each item in the list matches the provided example
maxArrayLikeEnsure that each item in the list matches the provided example and the list is no bigger than the provided max
minArrayLikeEnsure that each item in the list matches the provided example and the list is no smaller than the provided min

For example:

    DslPart body = new PactDslJsonBody()
        .minArrayLike("users", 1)
            .id()
            .stringType("name")
            .closeObject()
        .closeArray();

This will ensure that the users list is never empty and that each user has an identifier that is a number and a name that is a string.

You can specify the number of example items to generate in the array. The default is 1.

    DslPart body = new PactDslJsonBody()
        .minArrayLike("users", 1, 2)
            .id()
            .stringType("name")
            .closeObject()
        .closeArray();

Ignoring the list order (V4 specification)​

If the order of the list items is not known, you can use the unorderedArray matcher functions. These will match the actual list against the expected one, except will match the items in any order.

functiondescription
unorderedArrayEnsure that the list matches the provided example, ignoring the order
unorderedMinArrayEnsure that the list matches the provided example and the list is not smaller than the provided min
unorderedMaxArrayEnsure that the list matches the provided example and the list is no bigger than the provided max
unorderedMinMaxArrayEnsure that the list matches the provided example and the list is constrained to the provided min and max

Array contains matcher (V4 specification)​

The array contains matcher functions allow you to match the actual list against a list of required variants. These work by matching each item against the variants, and the matching succeeds if each variant matches at least one item. Order of items in the list is not important.

The variants can have a totally different structure, and can have their own matching rules to apply. For an example of how these can be used to match a hypermedia format like Siren, see Example Pact + Siren project.

functiondescription
arrayContainingMatches the items in an array against a number of variants. Matching is successful if each variant occurs once in the array. Variants may be objects containing matching rules.
.arrayContaining("actions")
  .object()
    .stringValue("name", "update")
    .stringValue("method", "PUT")
    .matchUrl("href", "http://localhost:9000", "orders", regex("\\d+", "1234"))
  .closeObject()
  .object()
    .stringValue("name", "delete")
    .stringValue("method", "DELETE")
    .matchUrl("href", "http://localhost:9000", "orders", regex("\\d+", "1234"))
  .closeObject()
.closeArray()

Root level arrays that match all items​

If the root of the body is an array, you can create PactDslJsonArray classes with the following methods:

functiondescription
arrayEachLikeEnsure that each item in the list matches the provided example
arrayMinLikeEnsure that each item in the list matches the provided example and the list is no bigger than the provided max
arrayMaxLikeEnsure that each item in the list matches the provided example and the list is no smaller than the provided min

For example:

PactDslJsonArray.arrayEachLike()
    .date("clearedDate", "mm/dd/yyyy", date)
    .stringType("status", "STATUS")
    .decimalType("amount", 100.0)
    .closeObject()

This will then match a body like:

[ {
  "clearedDate" : "07/22/2015",
  "status" : "C",
  "amount" : 15.0
}, {
  "clearedDate" : "07/22/2015",
  "status" : "C",
  "amount" : 15.0
}, {

  "clearedDate" : "07/22/2015",
  "status" : "C",
  "amount" : 15.0
} ]

You can specify the number of example items to generate in the array. The default is 1.

Matching JSON values at the root​

For cases where you are expecting basic JSON values (strings, numbers, booleans and null) at the root level of the body and need to use matchers, you can use the PactDslJsonRootValue class. It has all the DSL matching methods for basic values that you can use.

For example:

.consumer("Some Consumer")
.hasPactWith("Some Provider")
    .uponReceiving("a request for a basic JSON value")
        .path("/hello")
    .willRespondWith()
        .status(200)
        .body(PactDslJsonRootValue.integerType())

Matching any key in a map​

The DSL has been extended for cases where the keys in a map are IDs. For an example of this, see #313. In this case you can use the eachKeyLike method, which takes an example key as a parameter.

For example:

DslPart body = new PactDslJsonBody()
  .object("one")
    .eachKeyLike("001", PactDslJsonRootValue.id(12345L)) // key like an id mapped to a matcher
  .closeObject()
  .object("two")
    .eachKeyLike("001-A") // key like an id where the value is matched by the following example
      .stringType("description", "Some Description")
    .closeObject()
  .closeObject()
  .object("three")
    .eachKeyMappedToAnArrayLike("001") // key like an id mapped to an array where each item is matched by the following example
      .id("someId", 23456L)
      .closeObject()
    .closeArray()
  .closeObject();

For an example, have a look at ArticlesTest.

Combining matching rules with AND/OR​

Matching rules can be combined with AND/OR. There are two methods available on the DSL for this. For example:

DslPart body = new PactDslJsonBody()
  .numberValue("valueA", 100)
  .and("valueB","AB", PM.includesStr("A"), PM.includesStr("B")) // Must match both matching rules
  .or("valueC", null, PM.date(), PM.nullValue()) // will match either a valid date or a null value

The and and or methods take a variable number of matchers (varargs).

Overriding the handling of a body data type​

NOTE: version 4.1.3+

By default, bodies will be handled based on their content types. For binary contents, the bodies will be base64 encoded when written to the Pact file and then decoded again when the file is loaded. You can change this with an override property: pact.content_type.override.<TYPE>.<SUBTYPE>=text|binary|json. For instance, setting pact.content_type.override.application.pdf=text will treat PDF bodies as a text type and not encode/decode them.

Matching on paths​

You can use regular expressions to match incoming requests. The DSL has a matchPath method for this. You can provide a real path as a second value to use when generating requests, and if you leave it out it will generate a random one from the regular expression.

For example:

  .given("test state")
    .uponReceiving("a test interaction")
        .matchPath("/transaction/[0-9]+") // or .matchPath("/transaction/[0-9]+", "/transaction/1234567890")
        .method("POST")
        .body("{\"name\": \"harry\"}")
    .willRespondWith()
        .status(200)
        .body("{\"hello\": \"harry\"}")

Matching on headers​

You can use regular expressions to match request and response headers. The DSL has a matchHeader method for this. You can provide an example header value to use when generating requests and responses, and if you leave it out it will generate a random one from the regular expression.

For example:

  .given("test state")
    .uponReceiving("a test interaction")
        .path("/hello")
        .method("POST")
        .matchHeader("testreqheader", "test.*value")
        .body("{\"name\": \"harry\"}")
    .willRespondWith()
        .status(200)
        .body("{\"hello\": \"harry\"}")
        .matchHeader("Location", ".*/hello/[0-9]+", "/hello/1234")

Matching on query parameters​

You can use regular expressions to match request query parameters. The DSL has a matchQuery method for this. You can provide an example value to use when generating requests, and if you leave it out it will generate a random one from the regular expression.

For example:

  .given("test state")
    .uponReceiving("a test interaction")
        .path("/hello")
        .method("POST")
        .matchQuery("a", "\\d+", "100")
        .matchQuery("b", "[A-Z]", "X")
        .body("{\"name\": \"harry\"}")
    .willRespondWith()
        .status(200)
        .body("{\"hello\": \"harry\"}")

Debugging pact failures​

When the test runs, Pact will start a mock provider that will listen for requests and match them against the expectations you setup in createFragment. If the request does not match, it will return a 500 error response.

Each request received and the generated response is logged using SLF4J. Just enable debug level logging for au.com.dius.pact.consumer.UnfilteredMockProvider. Most failures tend to be mismatched headers or bodies.

Changing the directory pact files are written to​

By default, pact files are written to target/pacts (or build/pacts if you use Gradle), but this can be overwritten with the pact.rootDir system property. This property needs to be set on the test JVM as most build tools will fork a new JVM to run the tests.

For Gradle, add this to your build.gradle:

test {
    systemProperties['pact.rootDir'] = "$buildDir/custom-pacts-directory"
}

For maven, use the systemPropertyVariables configuration:

<project>
  [...]
  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>2.18</version>
        <configuration>
          <systemPropertyVariables>
            <pact.rootDir>some/other/directory</pact.rootDir>
            <buildDirectory>${project.build.directory}</buildDirectory>
            [...]
          </systemPropertyVariables>
        </configuration>
      </plugin>
    </plugins>
  </build>
  [...]
</project>

For SBT:

fork in Test := true,
javaOptions in Test := Seq("-Dpact.rootDir=some/other/directory")

Using @PactDirectory annotation​

You can override the directory the pacts are written in a test by adding the @PactDirectory annotation to the test class.

Forcing pact files to be overwritten (3.6.5+)​

By default, when the pact file is written, it will be merged with any existing pact file. To force the file to be overwritten, set the Java system property pact.writer.overwrite to true.

Publishing your pact files to a pact broker

If you use Gradle, you can use the pact Gradle plugin to publish your pact files.

Pact Specification V3

Version 3 of the pact specification changes the format of pact files in the following ways:

  • Query parameters are stored in a map form and are un-encoded (see #66 and #97 for information on what this can cause).
  • Introduces a new message pact format for testing interactions via a message queue.
  • Multiple provider states can be defined with data parameters.

Generating V2 spec pact files​

To have your consumer tests generate V2 format pacts, you can set the specification version to V2. If you're using the ConsumerPactTest base class, you can override the getSpecificationVersion method. For example:

    @Override
    protected PactSpecVersion getSpecificationVersion() {
        return PactSpecVersion.V2;
    }

If you are using the PactProviderRule, you can pass the version into the constructor for the rule.

    @Rule
    public PactProviderRule mockTestProvider = new PactProviderRule("test_provider", PactSpecVersion.V2, this);

Consumer test for a message consumer​

For testing a consumer of messages from a message queue, the MessagePactProviderRule rule class works in much the same way as the PactProviderRule class for Request-Response interactions, but will generate a V3 format message pact file.

For an example, look at ExampleMessageConsumerTest

Matching message metadata​

You can also use matching rules for the metadata associated with the message. There is a MetadataBuilder class to help with this. You can access it via the withMetadata method that takes a Java Consumer on the MessagePactBuilder class.

For example:

builder.given("SomeProviderState")
    .expectsToReceive("a test message with metadata")
    .withMetadata(md -> {
        md.add("metadata1", "metadataValue1");
        md.add("metadata2", "metadataValue2");
        md.add("metadata3", 10L);
        md.matchRegex("partitionKey", "[A-Z]{3}\\d{2}", "ABC01");
    })
    .withContent(body)
    .toPact();

Having values injected from provider state callbacks (3.6.11+)

You can have values from the provider state callbacks be injected into most places (paths, query parameters, headers, bodies, etc.). This works by using the V3 spec generators with provider state callbacks that return values. One example of where this would be useful is API calls that require an ID which would be auto-generated by the database on the provider side, so there is no way to know what the ID would be beforehand.

The following DSL methods all you to set an expression that will be parsed with the values returned from the provider states:

For JSON bodies, use valueFromProviderState.
For headers, use headerFromProviderState.
For query parameters, use queryParameterFromProviderState.
For paths, use pathFromProviderState.

For example, assume that an API call is made to get the details of a user by ID. A provider state can be defined that specifies that the user must be exist, but the ID will be created when the user is created. So we can then define an expression for the path where the ID will be replaced with the value returned from the provider state callback.

    .pathFromProviderState("/api/users/${id}", "/api/users/100")

You can also just use the key instead of an expression:

    .valueFromProviderState('userId', 'userId', 100) // will look value using userId as the key

Overriding the expression markers ${ and } (4.1.25+)​

You can change the markers of the expressions using the following system properties:

  • pact.expressions.start (default is ${)
  • pact.expressions.end (default is })

Dealing with persistent HTTP/1.1 connections (Keep Alive)​

As each test will get a new mock server, connections can not be persisted between tests. HTTP clients can cache connections with HTTP/1.1, and this can cause subsequent tests to fail. See #342 and #1383.

One option (if the HTTP client supports it, Apache HTTP Client does) is to set the system property http.keepAlive to false in the test JVM. The other option is to set pact.mockserver.addCloseHeader to true to force the mock server to send a Connection: close header with every response (supported with Pact-JVM 4.2.7+).

Test Analytics

We are tracking anonymous analytics to gather important usage statistics like JVM version and operating system. To disable tracking, set the 'pact_do_not_track' system property or environment variable to 'true'.