Top-level/standalone @ConfigureWireMock handling

[j-klingstedt]

Would it be possible to have the WireMockContextCustomizerFactory handle both @ConfigureWireMock annotations nested within @EnableWireMock (as it works right now) as well as "top-level", or standalone?

Our use-case is that we have an integration-test meta-annotation that includes a number of other annotations, mainly for convenience and to not have to repeat stuff over and over again. On a couple of the included annotations, we use @AliasFor to rewrite/alias properties, but since the WireMock Spring Boot starter afaik only takes the nested configuration annotation into account, we won't be able to go the alias way.

I realize that this might of course lead to questions regarding priority in case both exist.

[tomasbjerre]

Hi @j-klingstedt, long time no see!

So you want to be able to do something like this?

@SpringBootTest
@ConfigureWireMock(name = "mywiremock", registerSpringBean = true)
class AutowireNamedWireMockServerTest { }

And it would be same as this?

@SpringBootTest
@EnableWireMock(@ConfigureWireMock(name = "mywiremock", registerSpringBean = true))
class AutowireNamedWireMockServerTest { }

[j-klingstedt]

Yeah, indeed a long time :-) Hope you're doing well.

Yes, that's basically what we'd like to be able to do. Right now, our tests look (over-simplified) something like:

@IntegrationTest(files = "....")
class SomeIT { ... }

and we'd like to have our meta-annotation be something like:

@Retention(RUNTIME)
@Target(TYPE)
@SpringBootTest
@EnableWireMock
@ConfigureWireMock(...)
...other included annotations...
public @interface IntegrationTest {

    @AliasFor(annotation = ConfigureWireMock.class, attribute = "filesUnderClasspath")
    String files();

   ... other attributes and aliases/overrides...
}

As stated before, I don't know if this is feasible or not, but it'd be nice to not have to do manual workarounds on a quite large codebase.