wiremock | A tool for mocking HTTP services | Mock library

The mapping should be made to $PWD:/home/wiremock/mappings where PWD has the json files.

Also json files should look like this:

The Junit4 is available because of Testcontainer dependency. Testcontainers have a dependency on Junit4 and have it available by default. You might also encounter the following issue in few cases:

• IDE's detects the test cases written in Junit4 format but in sometime in case you make the test classes and methods package-private, they don't detect it.

I am not sure if they would be removing it in further releases but they do have Junit5 support which should resolve the issue

• https://www.testcontainers.org/test_framework_integration/junit_5/

Lower port ranges are sometimes not allowed. Can you try higher port ranges ?

Currently you would need to write a ResponseDefinitionTransformer to get the behaviour you're looking for.

It would need to check whether the ResponseDefinition passed in the parameter required a file, then if so check whether the file exists by doing something like:

I have never used Braintree SDK, but from what I see you use it by providing the Environment to the BraintreeGateway object: https://github.com/braintree/braintree_java/tree/master#quick-start-example

I would create a dedicated test Environment instance containing Wiremock URLs and provide it to the BraintreeGateway in my integration tests.

So Simon Martinelli helped me by finding the solution inside stackoverflow. After removing the hole config class, i got this "DSLContext that could not be found" error. Then i found this question:

How to fix "Consider defining a bean of type 'org.jooq.DSLContext' in your configuration." after update to jOOQ 3.15.0

Which solved my problem completly. Sorry for asking a question that has already been solved, but nothing pointed into the direction of R2dbcAutoConfiguration.

So, as Simon already said, removing the config class and, as the answer in this question already pointed out, adding @SpringBootApplication(exclude = { R2dbcAutoConfiguration.class }) solved the problem.

There were two issues causing problems: making sure the jdbcTemplate used in the callback method was configured with the correct DataSource, and making sure that the data in the embedded in memory DB was accessible from the MockServer response generation thread.

I solved the first problem by using a lambda or closure for the MockServer callback in which I use the JdbcTemplate instance created in the test class with the autowired DataSource (though solutions exist for the callback class approach as well).

The second problem was the result of the fact that the test method was within a transaction and so inserts to the DB made at the beginning of the test were not committed when the MockServer thread (note that the MockServer response generation happens in a different thread than the main thread where the test method is running) was executing the callback. Thus those inserts were not accessible to the callback.

The solution was to annotate the test method with @Transactional(propagation = Propagation.NOT_SUPPORTED) See h2 database access to test data from separate threads

There are a couple of reasons why this isn't sending anything to WireMock at the moment:

1. WireMock only accepts relative URLs when stubbing so passing the full URL including protocol and domain won't work. Try something equivalent to stubFor(post(urlPathEqualTo("/v1/private/product-reviews/business-units//invitation-links") instead.
2. There doesn't seem to be any way for your class under test to know which host/port WireMock is running on and no forward proxying set up so the code is presumably still trying to call the real Trustpilot API.

To solve 2. you have a couple of options:

1. Set up your class/code under test to use localhost as the destination host and the result of wireMockRule.port() as the port number, or wireMockRule.httpsPort() if you're on HTTPS.
2. Use the new auto JVM proxy setup feature to proxy your app's calls through WireMock. This assumes you're on WireMock 2.31.0+ and that your app's HTTP client respects the JVM proxy system properties.

From wiremock-user Google Group

If you don't need to match anything in particular for that element you could use a JSON placeholder e.g. "Resource": "${json-unit.any-string}".

If you do need to match the part after the port number then you can use the regex form e.g.: "Resource": "${json-unit.regex}.*/piwebapi/assetdatabases/D0NxzXSxtlKkGzAaZhKOB-KABJ2buwfWrkye3YhdL2FOUAUEhMQUZTMDRcQgYUUEVSRk9STUFOQ0UgVEVTVElORw/elements"}"