More test samples and support for passing objects in on pact construction

[holly-cummins]

At the moment, the consumer test does the following:

    private static final String alpacaBody = " {\n" +
            "      \"colour\": \"black\",\n" +
            "          \"name\": \"floppy\"\n" +
            "        }";

...

        // Here we define our mock, which is also our expectations for the provider

        return builder.given("test GET")
                .uponReceiving("GET REQUEST")
                .path("/alpaca")
                .method("GET")
                .willRespondWith()
                .status(200)
                .headers(headers)
                .body(alpacaBody)
                .toPact(V4Pact.class);

That should always work, but it would be nice to be able to do

    private static final Alpaca alpaca = new Alpaca("black", "floppy");

...

        // Here we define our mock, which is also our expectations for the provider

        return builder.given("test GET")
                .uponReceiving("GET REQUEST")
                .path("/alpaca")
                .method("GET")
                .willRespondWith()
                .status(200)
                .headers(headers)
                .body(alpaca)
                .toPact(V4Pact.class);

That works with Rest Assured. This would probably be a change to feed back to the Pact library, perhaps by allowing it to be initialised with an object mapper and then us auto-magically handing over the object mapper?

Alternatively, we should include some tests which manually inject the object mapper and create the json. There's no extension-specific magic, but it's a useful example to be able to follow.

[holly-cummins]

Injected objects aren't available in the @Pact body, which makes this harder. In Quarkus 3, we will need to check if they are.