You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2022/06/14 08:23:22 UTC

[GitHub] [camel-quarkus] jamesnetherton commented on pull request #3847: CamelTestSupport style of testing #3511

jamesnetherton commented on PR #3847:
URL: https://github.com/apache/camel-quarkus/pull/3847#issuecomment-1154871438

   I think we should create a new top level module for this stuff. I see `integration-tests-support` as an internal thing to support our project and not something that we put into the hands of our users.
   
   So maybe we do like Quarkus does and have `test-framework` module where we can build up a set of testing libraries. So initially something like `test-framework/junit5`. Which would give us an artifact named similar to the plain Camel equivalent `org.apache.camel.quarkus:camel-quarkus-junit5`.
   
   
   Agree with @essobedo that annotation driven tests would be good to have eventually. The more consistency we have with the other Camel runtimes, the better it is for our users. But lets take things one step at a time....
   
   


-- 
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-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org