anchor.diff:  ----
   
   Notice that we use @`DirtiesContext` on the test methods to force
  -link:spring-testing.html[Spring Testing] to automatically reload the
  -link:camelcontext.html[`CamelContext`] after each test method - this
  +link:spring-testing.adoc[Spring Testing] to automatically reload the
  +link:camelcontext.adoc[`CamelContext`] after each test method - this
   ensures that the tests don't clash with each other (e.g. one test method
   sending to an endpoint that is then reused in another test method).
   
  
positive.code: Spring Test with XML Config Example
  +++++++++++++++++++++++++++++++++++
  
  Here is the link:spring-testing.html[Spring Testing]
  link:../../../components/camel-spring/src/test/java/org/apache/camel/spring/patterns/FilterTest.java[example
  using XML Config]:
  
  
negative.code: Testing is a crucial activity in any piece of software development or
  integration. Typically Camel Riders use various different
  link:components.html[technologies] wired together in a variety of
  link:enterprise-integration-patterns.adoc[patterns] with different
  link:languages.html[expression languages] together with different forms
  of link:bean-integration.adoc[Bean Integration] and
  link:dependency-injection.adoc[Dependency Injection] so its very easy
  for things to go wrong! {icon-frown}. Testing is the crucial weapon to ensure
  that things work as you would expect {icon-smile}.
  
  