[camel-spring-boot-examples] branch master updated: Fix test with incorrect producerTemplate position

[acosentino]

This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-spring-boot-examples.git


The following commit(s) were added to refs/heads/master by this push:
     new 3d690d3  Fix test with incorrect producerTemplate position
3d690d3 is described below

commit 3d690d387e1245f66a4c1655884a0be23c6fde7d
Author: Farid Guliyev <fg7...@gmail.com>
AuthorDate: Mon Nov 2 09:39:49 2020 -0500

    Fix test with incorrect producerTemplate position
---
 .../src/test/java/CamelSplitterEIPTests.java                       | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git 
a/camel-example-spring-boot-splitter-eip/src/test/java/CamelSplitterEIPTests.java
 
b/camel-example-spring-boot-splitter-eip/src/test/java/CamelSplitterEIPTests.java
index 3566679..ffdfcf3 100644
--- 
a/camel-example-spring-boot-splitter-eip/src/test/java/CamelSplitterEIPTests.java
+++ 
b/camel-example-spring-boot-splitter-eip/src/test/java/CamelSplitterEIPTests.java
@@ -121,15 +121,14 @@ public class CamelSplitterEIPTests {
                mockH.reset();
                mockJ.reset();
 
-               // 'E' is poison message which will lead to an error during 
aggregation
-               
producerTemplate.sendBody("direct:split-aggregate-stop-on-aggregation-exception",
 "A,B,E,C,D");
-
-               // TODO : THOSE TESTS ARE NOT CORRECT, ANY VALUE WOULD PASS
                // Received all messages that went into aggregation, including 
corrupted one
                mockH.expectedBodiesReceived("A", "B", "E");
                // Since aggregation stopped, receiving all original messages
                mockJ.expectedBodiesReceived("A,B,E,C,D");
 
+               // 'E' is poison message which will lead to an error during 
aggregation
+               
producerTemplate.sendBody("direct:split-aggregate-stop-on-aggregation-exception",
 "A,B,E,C,D");
+
                mockH.assertIsSatisfied();
                mockJ.assertIsSatisfied();
        }