Hi, I tend to agree with Claus, camel-test-infra should be used only for integration tests for the reasons raised by Claus but also due to its name. It would be really misleading for the community to have to depend on an artifact called camel-test-infra for a unit test don't you agree?
In camel-test-junit5, Maybe we should do the same as what has been done in camel-test-main-junit5 where developers can decide to either extend CamelMainTestSupport or to use annotations like in SpringBoot and Quarkus or simply move the core logic of camel-test-infra into camel-test-junit5 and make camel-test-infra depends on camel-test-junit5, WDYT? Regards, Nicolas As a recipient of an email from the Talend Group, your personal data will be processed by our systems. Please see our Privacy Notice <https://www.talend.com/privacy-policy/> for more information about our collection and use of your personal information, our security practices, and your data protection rights, including any rights you may have to object to automated-decision making or profiling we use to analyze support or marketing related communications. To manage or discontinue promotional communications, use the communication preferences portal<https://info.talend.com/emailpreferencesen.html>. To exercise your data protection rights, use the privacy request form<https://talend.my.onetrust.com/webform/ef906c5a-de41-4ea0-ba73-96c079cdd15a/b191c71d-f3cb-4a42-9815-0c3ca021704cl>. Contact us here <https://www.talend.com/contact/> or by mail to either of our co-headquarters: Talend, Inc.: 400 South El Camino Real, Ste 1400, San Mateo, CA 94402; Talend SAS: 5/7 rue Salomon De Rothschild, 92150 Suresnes, France
