aldettinger commented on PR #3847: URL: https://github.com/apache/camel-quarkus/pull/3847#issuecomment-1181371859
In my opinion, that totally makes sense. Camel has been there for a long time and there are large camel-test bases out there. Offering something to simplify the migration path from camel 2.x to camel-quarkus is a good value, even if there are manual steps involved. On Tue, Jul 12, 2022 at 8:23 AM JiriOndrusek ***@***.***> wrote: > I meant this PoC like a first step in recommended migration of the tests. > If user has a lot of tests based on CamelTestSupport and would like to > try the CQ in no time. It should be nice to replace CamelTestSupport with > CamelQuarkusTestSupport, annotate test classes with @QuarkusTest and be > able to run those tests in JVM. > > This PoC is not meant to bring a better approach of testing (like > apache/camel#7041 <https://github.com/apache/camel/pull/7041> in Camel). > > I can imagine that there will be another step, which would allow users to > migrate their tests into the newer way of testing. And in that time, > CamelQuarkusTestSupport should reflect that. Migration quide (from the CamelQuarkusTestSupport > into the new way of testing) should be provided. > > @zbendhiba <https://github.com/zbendhiba> , @aldettinger > <https://github.com/aldettinger> what do you think about this approach? > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/camel-quarkus/pull/3847#issuecomment-1181364093>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AFJABNJQZ24MN5KJLA4MRE3VTUFPHANCNFSM5YUDV7TQ> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
