Leverage test instead of using main app

[GoncaloPT]

Hi,
Is your feature request related to a problem? Please describe.
We would like to avoid mixing up test related code/profiles with our src. This would also help us in leveraging the already existing setup for @SpringBootTests ( spin up kafka, mockserver, postgres, etc ), instead of duplicating everything for the ijhttp integration tests.

Describe the solution you'd like
Would like a way of connecting the integration-test of ijhttp with a springboottest class.

PS: Btw, I've added a comment on a LinkedIn page, sorry for the "spam" :)

[vitalijr2]

How I see the implementation: there is a special annotation (something like ParametrizedTest from jUnit5) that can run tests from one *.http files or bunch tests from *.http files in a directory, e.g. test/resources/http-client-test.

Then we just add to a test class (annotated with @WebMvcTest) an empty test method (annotated with @HttpClientTest) and it runs all test from *.http files that we set as parameter of our annotation.

[GoncaloPT]

Seems a very good implementation idea!
Let me know if you want some external contribution; we are very interested in making this grow :)

Workaround

For now, we managed to configure our build in a way that we can leverage the testing classpath by using ( leaving this just as a reference to others, since you're implementation if a far better idea ):

In the pom.xml:

<plugin>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-maven-plugin</artifactId>
    <executions>
        <execution>
            <id>start-integration-spring</id>
            <phase>pre-integration-test</phase>
            <configuration>
                <skip>${skipITs}</skip>
                <useTestClasspath>true</useTestClasspath>
                <mainClass>*****.IntegrationTestsEntryPoint</mainClass>
                <directories>
                    <directory>${project.build.testOutputDirectory}</directory>
                </directories>
            </configuration>
            <goals>
                <goal>start</goal>
            </goals>
        </execution>
        <execution>
            <id>stop-integration-spring</id>
            <phase>post-integration-test</phase>
            <configuration>
            </configuration>
            <goals>
                <goal>stop</goal>
            </goals>
        </execution>
    </executions>
</plugin>

Then in your main class ( in this case kotlin but java would use the same ):

@SpringBootApplication
@Import(
    WithPostgres::class,
    WithMockServer::class,
    WithPostgres::class,
    WithRedis::class
)
open class IntegrationTestsEntryPoint {

    companion object {
        @JvmStatic
        fun main(args: Array<String>) {
            SpringApplication.run(Application::class.java, *args)
        }
    }

}

The With** imports are just TestConfiguration classes with expose the TestContainer beans.

[vitalijr2]

Just note about my next steps.

I have investigated how to implement jUnit extension: unfortunately we cannot replace a test itself, we can run our code before or after test.

I have decided to go another way like other solutions already use, see Spring Boot Testing: MockMvc vs. WebTestClient vs. TestRestTemplate: to implement a builder-style component to customize command line and execute it.

[vitalijr2]

Now implementation is in the develop branch

[vitalijr2]

Implemented in v1.1.1