ppalaga commented on issue #2155: URL: https://github.com/apache/camel-quarkus/issues/2155#issuecomment-764574152
> We should also get rid of `CAMEL_QUARKUS_START_MOCK_BACKEND` because it makes little sense when tests require other environment variables to talk to the real service. It is true that many tests can autodetect based on the defined env vars whether they should start the mock or run against the real backend. In that sense, `CAMEL_QUARKUS_START_MOCK_BACKEND` can really be seen as useless. However, I think `CAMEL_QUARKUS_START_MOCK_BACKEND` is still useful, when it comes to preventing misconfiguration: Say, a new test comes in for which the tester has not set the env vars yet. IMO, in such situation, `CAMEL_QUARKUS_START_MOCK_BACKEND` is the only way how the tester can figure out that has not configured something yet. Yes, it is more work for the test authors, but IMO it pays back by giving more certainty that the tester is testing against the real backend without any silent fallback to mocks. ---------------------------------------------------------------- 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: us...@infra.apache.org
