Hello, I've been looking at this issue with running integration tests in Camel + SpringBoot combo context.
I have a route that fails to start in integration tests when CamelContext starts up. That's expected. One of endpoints refers to a AWS resource that the test running machine has no access to. That's OK too, I don't want to poke the real resource in the test, so I use the adviceWith() to replace the endpoint and start the camel context myself. This works well for a single test. As soon as I add another test, the second test fails, because of the complaints from the original endpoint about the permissions. It looks as if before the second test runs the spring context starts up together with the camel context (it seems to ignore the fact that the test class is annotated with @UseAdviceWith). This is a minimal testcase I could produce to reproduce the behaviour https://gist.github.com/anonymous/626cf26197dd5a05569d4d306870a22e What am I missing? Best, Artur
