anchor.diff:  You can find more information in <<cdi.adoc#CDI-Auto-detectingCamelroutes,auto-detecting Camel
   routes>>.
   
  +In case you prefer declaring the `RouteBuilder` bean in a separate class,
  +for example to share it more easily across multiple test classes, you can use
  +the `@Beans` annotation to instruct Camel CDI test to deploy that class as a
  +CDI bean, e.g.:
  +
  +[source,java]
  +----
  +@RunWith(CamelCdiRunner.class)
  +@Beans(classes = TestRoute.class)
  +public class CamelCdiTest {
  +
  +    // ...
  +}
  +----
  +
   [[CDITesting-Beanalternatives]]
   Bean alternatives
   +++++++++++++++++
  
positive.code: }
  ----
  
  If your using Arquillian as testing framework, you need to activate the
  alternative in your deployment method, e.g.:
  
  [source,java]
  
negative.code: ----
  
  One CDI container is bootstrapped for the entire execution of the test
  class.
  
  Besides, the test class is deployed as a CDI bean, so that you can
  control how the runner instantiate the test class, either one test class
  