This is an automated email from the ASF dual-hosted git repository.
aldettinger pushed a commit to branch CAMEL-13965
in repository https://gitbox.apache.org/repos/asf/camel.git
commit ee266f3559fe958265b57effa3858284fb831e18
Author: aldettinger <aldettin...@gmail.com>
AuthorDate: Thu Sep 12 20:20:10 2019 +0200
CAMEL-13965: Updated the camel-test-spring-junit5 documentation
---
.../src/main/docs/test-spring-junit5.adoc | 491 ++++-----------------
1 file changed, 76 insertions(+), 415 deletions(-)
diff --git
a/components/camel-test-spring-junit5/src/main/docs/test-spring-junit5.adoc
b/components/camel-test-spring-junit5/src/main/docs/test-spring-junit5.adoc
index 6afc889..be53e83 100644
--- a/components/camel-test-spring-junit5/src/main/docs/test-spring-junit5.adoc
+++ b/components/camel-test-spring-junit5/src/main/docs/test-spring-junit5.adoc
@@ -1,465 +1,126 @@
-= Test Spring JUnit5
+= Camel Test Spring JUnit 5
-*Available since 3.10*
+*Available since 3.0*
-Allows to test Camel with Spring applications such as Spring XML files or
Spring-Boot.
+The `camel-test-spring-junit5` module makes it possible to test Camel Spring
based application with JUnit 5.
-[IMPORTANT]
-====
-This documentation is old and needs to be updated
-====
+Testing is a crucial part of any development or integration work. The Spring
Framework offers a number of features that makes it easy to test while using
Spring for Inversion of Control.
-xref:manual::testing.adoc[Testing] is a crucial part of any development or
integration work. The Spring Framework offers a number of features that makes
it easy to test while using Spring for Inversion of Control which works with
JUnit 3.x, JUnit 4.x, and http://testng.org[TestNG].
+There are multiple approaches to test Camel Spring 5.x based routes with JUnit
5.
-We can use Spring for IoC and the Camel
xref:components::mock-component.adoc[Mock] and xref:components::test.adoc[Test]
endpoints to create sophisticated integration/unit tests that are easy to run
and debug inside your IDE. There are three supported approaches for testing
with Spring in Camel.
-[width="100%",cols="1,1,4,1",options="header",]
-|=======================================================================
-|Name |Testing Frameworks Supported |Description |Required Camel Test
Dependencies
-|<<camel-spring-test-support,Camel Spring Test Support>> a|
-* JUnit 3.x (deprecated)
-* JUnit 4.x
-* TestNG
-
-a|
-Provided by:
-
-* `org.apache.camel.test.CamelSpringTestSupport`
-* `org.apache.camel.test.junit4.CamelSpringTestSupport`
-* `org.apache.camel.testng.CamelSpringTestSupport`
-
-These base classes provide feature parity with the simple `CamelTestSupport`
classes from xref:components::test.adoc[Camel Test] but do not support Spring
annotations on the test class such as `@Autowired`, `@DirtiesContext`, and
`@ContextConfiguration`.
-
-a|
-* JUnit 3.x (deprecated) - camel-test-spring
-* JUnit 4.x - camel-test-spring
-* TestNG - camel-test-ng
-
-|<<plain-spring-test, Plain Spring Test>> a|
-* JUnit 3.x
-* JUnit 4.x
-* TestNG
-
-a|
-Either extend the abstract base classes:
-
-* `org.springframework.test.context.junit38.AbstractJUnit38SpringContextTests`
-* `org.springframework.test.context.junit38.AbstractJUnit4SpringContextTests`
-* etc.
-
-provided in Spring Test or use the Spring Test JUnit4 runner.
-
-These approaches support both the Camel annotations and Spring annotations.
However, they do NOT have
http://camel.apache.org/camel-test.html#CamelTest-FeaturesProvidedbyCamelTestSupport[feature
parity] with:
-
-* `org.apache.camel.test.CamelTestSupport`
-* `org.apache.camel.test.junit4.CamelTestSupport`
-* `org.apache.camel.testng.CamelSpringTestSupport`
-
-a|
-* JUnit 3.x (deprecated) - None
-* JUnit 4.x - None
-* TestNG - None
-
-|<<camel-enhanced-spring-test,Camel Enhanced Spring Test>> a|
-* JUnit 4.x
-* TestNG
-
-a|
-Either:
-
-* use the `org.apache.camel.test.junit4.CamelSpringJUnit4ClassRunner` runner
with the `@RunWith` annotation,
-* or extend `org.apache.camel.testng.AbstractCamelTestNGSpringContextTests` to
enable
http://camel.apache.org/camel-test.html#CamelTest-FeaturesProvidedbyCamelTestSupport[feature
parity] with `org.apache.camel.test.CamelTestSupport` and
`org.apache.camel.test.junit4.CamelTestSupport`. These classes support the full
suite of Spring Test annotations such as `@Autowired`, `@DirtiesContext`, and
`@ContextConfiguration`.
-
-a|
-* JUnit 3.x (deprecated) - camel-test-spring
-* JUnit 4.x - camel-test-spring
-* TestNG - camel-test-ng
-|=======================================================================
-
-[#camel-spring-test-support]
-== CamelSpringTestSupport
-
-The following Spring test support classes:
-
-* `org.apache.camel.test.CamelSpringTestSupport`
-* `org.apache.camel.test.junit4.CamelSpringTestSupport`, and
-* `org.apache.camel.testng.CamelSpringTestSupport`
-
-extend their non-Spring aware counterparts:
-
-* `org.apache.camel.test.CamelTestSupport`
-* `org.apache.camel.test.junit4.CamelTestSupport`, and
-* `org.apache.camel.testng.CamelTestSupport`
-
-and deliver integration with Spring into your test classes.
-
-Instead of instantiating the `CamelContext` and routes programmatically, these
classes rely on a Spring context to wire the needed components together. If
your test extends one of these classes, you must provide the Spring context by
implementing the following method.
-[source,java]
+== Extending the CamelSpringTestSupport class
+An approach is to extend
`org.apache.camel.test.spring.junit5.CamelSpringTestSupport`, for instance:
----
-protected abstract AbstractApplicationContext createApplicationContext();
-----
-You are responsible for the instantiation of the Spring context in the method
implementation. All of the features available in the non-Spring aware
counterparts from http://camel.apache.org/camel-test.html[Camel Test] are
available in your test.
-
-[#plain-spring-test]
-== Plain Spring Test
-
-In this approach, your test classes directly inherit from the Spring Test
abstract test classes or use the JUnit 4.x test runner provided in Spring Test.
This approach supports dependency injection into your test class and the full
suite of Spring Test annotations. However, it does not support the features
provided by the `CamelSpringTestSupport` classes.
-
-=== Plain Spring Test using JUnit 3.x with XML Config Example
+public class SimpleMockTest extends CamelSpringTestSupport {
-Here is a simple unit test using JUnit 3.x support from Spring Test using
http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/java/org/apache/camel/spring/patterns/FilterTest.java[XML
Config].
-[source,java]
-----
-// tag::example[]
-@ContextConfiguration
-public class FilterTest extends SpringRunWithTestSupport {
-
@EndpointInject("mock:result")
protected MockEndpoint resultEndpoint;
-
+
@Produce("direct:start")
protected ProducerTemplate template;
-
- @DirtiesContext
- @Test
- public void testSendMatchingMessage() throws Exception {
- String expectedBody = "<matched/>";
-
- resultEndpoint.expectedBodiesReceived(expectedBody);
-
- template.sendBodyAndHeader(expectedBody, "foo", "bar");
-
- resultEndpoint.assertIsSatisfied();
- }
-
- @DirtiesContext
- @Test
- public void testSendNotMatchingMessage() throws Exception {
- resultEndpoint.expectedMessageCount(0);
-
- template.sendBodyAndHeader("<notMatched/>", "foo",
"notMatchedHeaderValue");
-
- resultEndpoint.assertIsSatisfied();
- }
-}
-// end::example[]
-----
-Notice that we use `@DirtiesContext` on the test methods to force Spring
Testing to automatically reload the
http://camel.apache.org/camelcontext.html[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.
-
-Also notice the use of `@ContextConfiguration` to indicate that by default we
should look for the file
http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/resources/org/apache/camel/spring/patterns/FilterTest-context.xml[FilterTest-context.xml
on the classpath] to configure the test case. The test context looks like:
-[source,xml]
-----
-<!-- tag::example[] -->
-<beans xmlns="http://www.springframework.org/schema/beans";
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
- xmlns:context="http://www.springframework.org/schema/context";
- xsi:schemaLocation="
- http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
- http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
- ">
-
- <camelContext xmlns="http://camel.apache.org/schema/spring";>
- <route>
- <from uri="direct:start"/>
- <filter>
- <xpath>$foo = 'bar'</xpath>
- <to uri="mock:result"/>
- </filter>
- </route>
- </camelContext>
-
-</beans>
-<!-- end::example[] -->
-----
-This test will load a Spring XML configuration file called
`FilterTest-context.xml` from the classpath in the same package structure as
the `FilterTest` class and initialize it along with any Camel routes we define
inside it, then inject the `CamelContext` instance into our test case.
-For instance, like this maven folder layout:
-[source,text]
-----
-src/test/java/org/apache/camel/spring/patterns/FilterTest.java
-src/test/resources/org/apache/camel/spring/patterns/FilterTest-context.xml
-----
-
-=== Plain Spring Test Using JUnit 4.x With Java Config Example
+ @Override
+ protected AbstractApplicationContext createApplicationContext() {
+ return new
ClassPathXmlApplicationContext("org/apache/camel/test/patterns/SimpleMockTest.xml");
+ }
-You can completely avoid using an XML configuration file by using
http://camel.apache.org/spring-java-config.html[Spring Java Config]. Here is a
unit test using JUnit 4.x support from Spring Test using
http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring-javaconfig/src/test/java/org/apache/camel/spring/javaconfig/patterns/FilterTest.java[Java
Config].
-[source,text]
-----
-// tag::example[]
-@RunWith(CamelSpringJUnit4ClassRunner.class)
-@ContextConfiguration(classes = {FilterTest.ContextConfig.class}, loader =
CamelSpringDelegatingTestContextLoader.class)
-public class FilterTest extends AbstractJUnit4SpringContextTests {
-
- @EndpointInject("mock:result")
- protected MockEndpoint resultEndpoint;
-
- @Produce("direct:start")
- protected ProducerTemplate template;
-
- @DirtiesContext
@Test
- public void testSendMatchingMessage() throws Exception {
- String expectedBody = "<matched/>";
-
+ public void testMock() throws Exception {
+ String expectedBody = "Hello World";
resultEndpoint.expectedBodiesReceived(expectedBody);
-
template.sendBodyAndHeader(expectedBody, "foo", "bar");
-
- resultEndpoint.assertIsSatisfied();
- }
-
- @DirtiesContext
- @Test
- public void testSendNotMatchingMessage() throws Exception {
- resultEndpoint.expectedMessageCount(0);
-
- template.sendBodyAndHeader("<notMatched/>", "foo",
"notMatchedHeaderValue");
-
resultEndpoint.assertIsSatisfied();
}
-
- @Configuration
- public static class ContextConfig extends SingleRouteCamelConfiguration {
- @Bean
- public RouteBuilder route() {
- return new RouteBuilder() {
- public void configure() {
-
from("direct:start").filter(header("foo").isEqualTo("bar")).to("mock:result");
- }
- };
- }
- }
}
-// end::example[]
----
-This is similar to the XML Config example above except that there is no XML
file and instead the nested `ContextConfig` class does all of the
configuration; so your entire test case is contained in a single Java class. We
currently have to reference by class name this class in the
`@ContextConfiguration` which is a bit ugly. Please vote for
http://jira.springframework.org/browse/SJC-238[SJC-238] to address this and
make Spring Test work more cleanly with Spring JavaConfig.
-
-=== Plain Spring Test Using JUnit 4.0.x Runner With XML Config
-
-You can avoid extending Spring classes by using the `SpringJUnit4ClassRunner`
provided by Spring Test. This custom JUnit runner means you are free to choose
your own class hierarchy while retaining all the capabilities of Spring Test.
-
-TIP: This is for Spring 4.0.x. If you use Spring 4.1 or newer, then see the
next section.
+This approach provides feature parity with
`org.apache.camel.test.junit5.CamelTestSupport` from `camel-test-junit5` but
does not support Spring annotations on the test class such as `@Autowired`,
`@DirtiesContext`, and `@ContextConfiguration`.
+Instead of instantiating the `CamelContext` and routes programmatically, this
class relies on a Spring context to wire the needed components together. If
your test extends this class, you must provide the Spring context by
implementing the following method.
[source,java]
----
-@RunWith(SpringJUnit4ClassRunner.class)
-@ContextConfiguration
-public class MyCamelTest {
- @Autowired
- protected CamelContext camelContext;
-
- @EndpointInject("mock:foo")
- protected MockEndpoint foo;
-
- @Test
- @DirtiesContext
- public void testMocksAreValid() throws Exception {
- // ...
-
- foo.message(0).header("bar").isEqualTo("ABC");
- MockEndpoint.assertIsSatisfied(camelContext);
- }
-}
+protected abstract AbstractApplicationContext createApplicationContext();
----
-=== Plain Spring Test Using JUnit 4.1.x Runner With XML Config
-
-You can avoid extending Spring classes by using the `SpringJUnit4ClassRunner`
provided by Spring Test. This custom JUnit runner means you are free to choose
your own class hierarchy while retaining all the capabilities of Spring Test.
-
-TIP: From *Spring 4.1*, you need to use the `@BootstrapWith` annotation to
configure it to use Camel testing, as shown below.
-
-[source,java]
+== Using the @CamelSpringTest annotation
+Another approach involves the usage of the
`org.apache.camel.test.spring.junit5.CamelSpringTest` annotation, for instance:
----
-@RunWith(CamelSpringJUnit4ClassRunner.class)
-@BootstrapWith(CamelTestContextBootstrapper.class)
-@ContextConfiguration
-public class MyCamelTest {
+@CamelSpringTest
+@ContextConfiguration()
+@DirtiesContext(classMode = ClassMode.AFTER_EACH_TEST_METHOD)
+public class CamelSpringPlainTest {
+
@Autowired
protected CamelContext camelContext;
-
- @EndpointInject("mock:foo")
- protected MockEndpoint foo;
-
- @Test
- @DirtiesContext
- public void testMocksAreValid() throws Exception {
- // ...
-
- foo.message(0).header("bar").isEqualTo("ABC");
- MockEndpoint.assertIsSatisfied(camelContext);
- }
-}
-----
-
-[#camel-enhanced-spring-test]
-== Camel Enhanced Spring Test
-
-Using the `org.apache.camel.test.junit4.CamelSpringJUnit4ClassRunner` runner
with the `@RunWith` annotation or extending
`org.apache.camel.testng.AbstractCamelTestNGSpringContextTests` provides the
full feature set of Spring Test with support for the feature set provided in
the `CamelTestSupport` classes.
-
-A number of Camel specific annotations have been developed in order to provide
for declarative manipulation of the Camel context(s) involved in the test.
These annotations free your test classes from having to inherit from the
`CamelSpringTestSupport` classes and also reduce the amount of code required to
customize the tests.
-[width="100%",cols="1,1,4,1,1",options="header",]
-|=======================================================================
-|Annotation Class |Applies To |Description |Default Behaviour If Not Present
|Default Behavior If Present
-|org.apache.camel.test.spring.DisableJmx a|Class a|
-Indicates if JMX should be globally disabled in the CamelContexts that are
bootstrapped during the test through the use of Spring Test loaded application
contexts. a|
-JMX is disabled a|JMX is disabled
-
-|org.apache.camel.test.spring.ExcludeRoutes a|Class a|
-Indicates if certain route builder classes should be excluded from discovery.
Initializes a `org.apache.camel.spi.PackageScanClassResolver` to exclude a set
of given classes from being resolved. Typically this is used at test time to
exclude certain routes, which might otherwise be just noisy, from being
discovered and initialized. a|
-Not enabled and no routes are excluded a|No routes are excluded
-
-Indicates if the CamelContexts that are bootstrapped during the test through
the use of Spring Test loaded application contexts should use lazy loading of
type converters. a|
-Type converters are not lazy loaded a|
-Type converters are not lazy loaded
-|org.apache.camel.test.spring.MockEndpoints a|Class a|
-Triggers the auto-mocking of endpoints whose URIs match the provided filter.
The default filter is `"*"` which matches all endpoints. See
`org.apache.camel.impl.InterceptSendToMockEndpointStrategy` for more details on
the registration of the mock endpoints. a|
-Not enabled a|All endpoints are sniffed and recorded in a mock endpoint.
+ @EndpointInject(value = "mock:a")
+ protected MockEndpoint mockA;
-|org.apache.camel.test.spring.MockEndpointsAndSkip a|Class a|
-Triggers the auto-mocking of endpoints whose URIs match the provided filter.
The default filter is `"*"`, which matches all endpoints. See
http://svn.apache.org/viewvc/camel/trunk/camel-core/src/main/java/org/apache/camel/impl/InterceptSendToMockEndpointStrategy.java?view=markup[org.apache.camel.impl.InterceptSendToMockEndpointStrategy]
for more details on the registration of the mock endpoints. This annotation
will also skip sending the message to matched endpoints as well. a|
-Not enabled a|All endpoints are sniffed and recorded in a mock endpoint. The
original endpoint is not invoked.
-
-|org.apache.camel.test.spring.ProvidesBreakpoint a|Method a|
-Indicates that the annotated method returns an
`org.apache.camel.spi.Breakpoint` for use in the test. Useful for intercepting
traffic to all endpoints or simply for setting a break point in an IDE for
debugging. The method must be public, static, take no arguments, and return
`org.apache.camel.spi.Breakpoint`. a|
-N/A a|
-The returned `Breakpoint` is registered in the CamelContext(s)
-
-|org.apache.camel.test.spring.ShutdownTimeout a|Class a|
-Indicates to set the shutdown timeout of all CamelContexts instantiated
through the use of Spring Test loaded application contexts. If no annotation
is used, the timeout is automatically reduced to 10 seconds by the test
framework. a|
-10 seconds a|10 seconds
-
-|org.apache.camel.test.spring.UseAdviceWith a|Class a|
-Indicates the use of `adviceWith()` within the test class. If a class is
annotated with this annotation and `UseAdviceWith#value()` returns true, any
CamelContexts bootstrapped during the test through the use of Spring Test
loaded application contexts will not be started automatically.
-
-The test author is responsible for injecting the Camel contexts into the test
and executing `CamelContext#start()` on them at the appropriate time after any
advice has been applied to the routes in the CamelContext(s). a|
-CamelContexts do not automatically start. a|CamelContexts do not automatically
start.
-
-|org.apache.camel.test.spring.UseOverridePropertiesWithPropertiesComponent
a|Method a|
-Indicates that the annotated method returns a `java.util.Properties` for use
in the test, and that those properties override any existing properties
configured on the `PropertiesComponent`. a|
-a|Override properties
-|=======================================================================
-
-The following example illustrates the use of the `@MockEndpoints` annotation
in order to setup mock endpoints as interceptors on all endpoints using the
Camel Log component and the `@DisableJmx` annotation to enable JMX which is
disabled during tests by default.
+ @EndpointInject(value = "mock:b")
+ protected MockEndpoint mockB;
-TIP: We still use the `@DirtiesContext` annotation to ensure that the
CamelContext, routes, and mock endpoints are reinitialized between test methods.
+ @Produce(value = "direct:start")
+ protected ProducerTemplate start;
-[source,java]
-----
-@RunWith(CamelSpringJUnit4ClassRunner.class)
-@BootstrapWith(CamelTestContextBootstrapper.class)
-@ContextConfiguration
-@DirtiesContext(classMode = ClassMode.AFTER_EACH_TEST_METHOD)
-@MockEndpoints("log:*")
-@DisableJmx(false)
-public class CamelSpringJUnit4ClassRunnerPlainTest {
- @Autowired
- protected CamelContext camelContext2;
-
- protected MockEndpoint mockB;
-
- @EndpointInject(value = "mock:c", context = "camelContext2")
- protected MockEndpoint mockC;
-
- @Produce("direct:start2", context = "camelContext2")
- protected ProducerTemplate start2;
-
- @EndpointInject(value = "mock:log:org.apache.camel.test.junit4.spring",
context = "camelContext2")
- protected MockEndpoint mockLog;
-
@Test
public void testPositive() throws Exception {
- mockC.expectedBodiesReceived("David");
- mockLog.expectedBodiesReceived("Hello David");
-
- start2.sendBody("David");
-
- MockEndpoint.assertIsSatisfied(camelContext);
- }
-----
+ assertEquals(ServiceStatus.Started, camelContext.getStatus());
+ mockA.expectedBodiesReceived("David");
+ mockB.expectedBodiesReceived("Hello David");
-== Adding More Mock Expectations
+ start.sendBody("David");
-If you wish to add any new assertions to your test you can easily do so with
the following. Notice how we use `@EndpointInject` to inject a Camel endpoint
into our code then the http://camel.apache.org/mock.html[Mock] API to add an
expectation on a specific message.
-[source,java]
-----
-@ContextConfiguration
-public class MyCamelTest extends AbstractJUnit38SpringContextTests {
- @Autowired
- protected CamelContext camelContext;
-
- @EndpointInject("mock:foo")
- protected MockEndpoint foo;
-
- public void testMocksAreValid() throws Exception {
- // lets add more expectations
- foo.message(0).header("bar").isEqualTo("ABC");
-
MockEndpoint.assertIsSatisfied(camelContext);
}
-}
-----
-
-== Further Processing the Received Messages
-
-Sometimes once a http://camel.apache.org/mock.html[Mock] endpoint has received
some messages you want to then process them further to add further assertions
that your test case worked as you expect.
-
-So you can then process the received message exchanges if you like...
-[source,java]
-----
-@ContextConfiguration
-public class MyCamelTest extends AbstractJUnit38SpringContextTests {
- @Autowired
- protected CamelContext camelContext;
-
- @EndpointInject("mock:foo")
- protected MockEndpoint foo;
-
- public void testMocksAreValid() throws Exception {
- // lets add more expectations...
-
- MockEndpoint.assertIsSatisfied(camelContext);
-
- // now lets do some further assertions
- List<Exchange> list = foo.getReceivedExchanges();
- for (Exchange exchange : list) {
- Message in = exchange.getIn();
- // ...
- }
+ @Test
+ public void testAnotherCase() throws Exception {
+ ...
}
}
----
-== Sending and Receiving Messages
-
-It might be that the
http://camel.apache.org/enterprise-integration-patterns.html[Enterprise
Integration Patterns] you have defined in either
http://camel.apache.org/spring.html[Spring] XML or using the Java
http://camel.apache.org/dsl.html[DSL] do all of the sending and receiving and
you might just work with the http://camel.apache.org/mock.html[Mock] endpoints
as described above. However sometimes in a test case its useful to explicitly
send or receive messages directly.
-
-To send or receive messages you should use the
http://camel.apache.org/bean-integration.html[Bean Integration] mechanism. For
example to send messages inject a `ProducerTemplate` using the
`@EndpointInject` annotation then call the various send methods on this object
to send a message to an endpoint. To consume messages use the `@MessageDriven`
annotation on a method to have the method invoked when a message is received.
-[source,java]
+The above test will load the route from
`org/apache/camel/test/spring/CamelSpringPlainTest-context.xml` which looks
like below:
----
-public class Foo {
- @EndpointInject("activemq:foo.bar")
- ProducerTemplate producer;
-
- public void doSomething() {
- // lets send a message!
- producer.sendBody("<hello>world!</hello>");
- }
-
- // lets consume messages from the 'cheese' queue
- @MessageDriven(uri="activemq:cheese")
- public void onCheese(String name) {
- // ...
- }
-}
+<?xml version="1.0" encoding="UTF-8"?>
+<beans xmlns="http://www.springframework.org/schema/beans";
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
+ xsi:schemaLocation="
+ http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
+ http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd ">
+
+ <camelContext id="camelContext"
+ xmlns="http://camel.apache.org/schema/spring"; trace="true"
+ autoStartup="true">
+ <packageScan>
+ <package>org.apache.camel.test.spring</package>
+ </packageScan>
+ <route>
+ <from uri="direct:start" />
+ <to uri="mock:a" />
+ <transform>
+ <simple>Hello ${body}</simple>
+ </transform>
+ <to uri="mock:b" />
+ </route>
+ </camelContext>
+
+ <bean id="bridgePropertyPlaceholder"
+
class="org.apache.camel.spring.spi.BridgePropertyPlaceholderConfigurer">
+ <property name="location"
+
value="classpath:org/apache/camel/test/spring/test.properties" />
+ </bean>
+</beans>
----
+This approach supports both Camel and Spring annotations, such as
`@Autowired`, `@DirtiesContext`, and `@ContextConfiguration`.
+However, it does NOT have feature parity with
`org.apache.camel.test.junit5.CamelTestSupport`.
+
== Migrating Camel Spring Tests from JUnit 4 to JUnit 5
-Find below some hints to help in migrating camel spring tests from JUnit 4 to
JUnit 5.
+Find below some hints to help in migrating Camel Spring tests from JUnit 4 to
JUnit 5.
-=== Referencing the Camel Test Spring JUnit5 library in your project
+=== Referencing the Camel Test Spring JUnit 5 library in your project
Projects using `camel-test-spring` would need to use
`camel-test-spring-junit5`. For instance, maven users would update their
pom.xml file as below:
----
<dependency>
@@ -469,11 +130,11 @@ Projects using `camel-test-spring` would need to use
`camel-test-spring-junit5`.
</dependency>
----
-Tips: It's possible to run JUnit4 & JUnit5 based camel spring tests side by
side including the following dependencies `camel-test-spring`,
-`camel-test-spring-junit5` and `junit-vintage-engine`. This configuration
allows to migrate a camel spring test at once.
+Tips: It's possible to run JUnit 4 & JUnit 5 based Camel Spring tests side by
side including the following dependencies `camel-test-spring`,
+`camel-test-spring-junit5` and `junit-vintage-engine`. This configuration
allows to migrate a Camel Spring test at once.
=== Typical migration steps linked to JUnit 5 support in Camel Spring Test
-* Migration steps linked to Camel Test Junit 5 itself should have been applied
+* Migration steps linked to Camel Test Junit 5 itself should have been applied
first
* Imports of `org.apache.camel.test.spring.\*` should be replaced with
`org.apache.camel.test.spring.junit5.*`
* Usage of `@RunWith(CamelSpringRunner.class)` should be replaced with
`@CamelSpringTest`
* Usage of `@BootstrapWith(CamelTestContextBootstrapper.class)` should be
replaced with `@CamelSpringTest`
