How should we migrate our generated project to @QuarkusIntegrationTest

[Andy Damevin]

Hey hey,

We had a discussion on Zulip about how we should migrate our generated project (cli, code.quarkus.io, ...) from @NativeImageTest to @QuarkusIntegrationTest (which started from this issue), but better have this discussion here.

As explained in the doc, using @QuarkusIntegrationTest, the packaging is defining how the integration test should be executed (native, jar, container). In other words, it's not only for native anymore.

Our current codegen generates native tests, they are named `NativeGreetingResourceIT` by default (also they are located in src/native-test/java when using gradle), also the maven failsafe configuration is only available with the native profile (which means that it won't get activated when native is enabled from something else than the native profile, right?).

The question here is to know if we should keep that naming or have a more generic `GreetingResourceIT` (located in src/it/java when using gradle)

If doing so, in the pom.xml, we should also move the failsafe configuration out of the native profile.

It would be nice to have your input on this.

Thanks,

--

Andy Damevin

[Stuart Douglas]

This all sounds reasonable IMHO.

Stuart

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CAE_u_P4n7knz1DsjMMUA_PJJdOQZpZ79dWLfh-C-VMDtq3oTGQ%40mail.gmail.com.

[Georgios Andrianakis]

I think we should do the renaming in order to make it evident what the @QuarkusIntegrationTest can do.

That way new projects generated when we release 2.2, will have the new setup

To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CAD%2BL2cyaEtEXbi%3DGATTO8N0SnW7E3Hthtt0X9vHR63RT35eeRQ%40mail.gmail.com.