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 2020/09/11 14:43:22 UTC

[GitHub] [camel-quarkus] ppalaga edited a comment on pull request #1782: Make sure that Telegram tests are not run against mock API by setting…

ppalaga edited a comment on pull request #1782:
URL: https://github.com/apache/camel-quarkus/pull/1782#issuecomment-691132555


   > Would community accept the `CAMEL_QUARKUS_START_MOCK_BACKEND` be set by default to `false`
   
   I discussed this with @jamesnetherton  and @oscerd and we prefer not to do that, because it would require all devs to export CAMEL_QUARKUS_START_MOCK_BACKEND=true
   
   @jamesnetherton came with an alternative proposal that is implemented in 7042574
   
   With this solution in place, you can do the following:
   
   * Run the tests with CAMEL_QUARKUS_START_MOCK_BACKEND=false
   * Count the occurrences of `<artifactId>camel-quarkus-integration-test-support-mock-backend</artifactId>` in `integration-tests/*/pom.xml`
   * Count the occurrences of `Real backend will be used for` in the output of all tests
   * The numbers should be non-null and equal (as long as you only run the JVM tests)
   * There should also be zero occurrences of `Mock backend will be used for` in the output of the tests
   
   WDYT?
   


----------------------------------------------------------------
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.

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