mockserver | MockServer enables easy mocking of any system | Proxy library

Looks like you're trying to convert from the Groovy DSL to Kotlin. Remember that in the Kotlin DSL, everything is strongly typed since Kotlin is strongly typed.

You need to wrap all tasks creations within the tasks { } block in order to access compileTestKotlin. Currently, the scope of this in your cucumber task registration is the task itself which is of type DefaultTask which does not know about compileTestKotlin.

Additionally:

• mainClassName is deprecated and mainClass should be used instead.
• The java extension provides the capability to create sources JAR for you, so no need to create the task yourself unless you have specific requirements for the JAR which does not seem to be the case from your snippet.
• Since the goal of the cucumber task is to execute a Java main class, you can utilize JavaExec as your task type instead of DefaultTask

Polished sample (untested):

I could get my tests running by removing any annotations under the package org.junit. All annotations are from org.junit.jupitor.

That baseUrl shouldn't be in the path property, which should just take the path, not the full URI

I.e. it should just be this

It's a bug in dotnet runtime: https://github.com/dotnet/runtime/issues/60628

Pending PR: https://github.com/dotnet/runtime/pull/64038

Posting @YouthDev's solution as an answer:

Thanks to @DougStevenson and @Deko in the comments, I switched to an axios library and it works like a charm. Thank you to both for pointing me in the correct direction. Below is the working axios code.

The idea of MockRestServiceServer is that it allows you mock the external server such that the RestTemplate does not really need to send the requests to the actual server during the testing. Instead it just sends the requests to this MockRestServiceServer (think that it is a kind of in-memory server) and it will return the configured mocked responses for the corresponding requests.

You have to configure all the expected requests that the MockRestServiceServer will received and its corresponding responds before the test.

So basically there are two things needed to be verified which are :

1. For every request sent by RestTemplate , there should be a mocked response configured for that request in the MockRestServiceServer

2. For all the requests that are to be expected to be received on the MockRestServiceServer , the RestTemplate should really send out all of these expected requests.

(1) will be verified automatically whenever the RestTemplate send out a request. The exception no further requests expected: HTTP that you mentioned is because it fails (1) (i.e. forget to stub this request in the MockRestServiceServer)

(2) will not be verified automatically . You have to call MockRestServiceServer.verify() manually in order to verify it.

An example :

The version of @PactTestFor method still needs to use version 3.

Although I was not able to find a answer to redirect webserver request to sideEffect class, For now atleast managing by Mockito's MockBean and Answer.

Stub the requests using Webmock.

It is recommended to stub every request you expect to make separately so you know exactly what is requested, but you can also use a syntax similar to what you asked for.