Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-10241

MockEndpointAndSkip and DirtiesContext not working

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Cannot Reproduce
    • Affects Version/s: 2.17.3
    • Fix Version/s: 2.21.0
    • Component/s: camel-test
    • Labels:
      None
    • Environment:

      java8
      spring boot 1.3.6

    • Estimated Complexity:
      Unknown

      Description

      MockEndpointAndSkip does not seem to get re-applied after each test when used in conjunction with DirtiesContext. Here is a unit test exhibiting the problem

      @RunWith(CamelSpringBootJUnit4ClassRunner.class)
      @SpringApplicationConfiguration
      @MockEndpointsAndSkip("direct:b")
      @DirtiesContext(classMode = ClassMode.AFTER_EACH_TEST_METHOD)
      public class MockTest {
      
      	@Produce(uri = "direct:a")
      	private ProducerTemplate producer;
      
      	@EndpointInject(uri = "mock:end")
      	private MockEndpoint end;
      
      	@EndpointInject(uri = "mock:direct:b")
      	private MockEndpoint directB;
      
      	@Autowired
      	private CamelContext context;
      
      	@Configuration
      	@EnableAutoConfiguration
      	public static class Config extends SpringRouteBuilder {
      
      		@Override
      		public void configure() throws Exception {
      			from("direct:a").to("direct:b");
      			from("direct:b").to("mock:end");
      		}
      	}
      
      	@Test
      	public void testMock() throws InterruptedException {
      		end.expectedMessageCount(0);
      		directB.expectedBodiesReceived("hello");
      
      		producer.sendBody("hello");
      
      		MockEndpoint.assertIsSatisfied(context);
      	}
      
      	@Test
      	public void testMock2() throws InterruptedException {
      		end.expectedMessageCount(0);
      		directB.expectedBodiesReceived("hello");
      
      		producer.sendBody("hello");
      
      		MockEndpoint.assertIsSatisfied(context);
      	}
      }
      

      testMock and testMock2 are exactly the same and if run individually, they pass. However if you run both, the second one will always fail. Running them both inside eclipse and from maven command line exhibit the same behaviour.

      The error I get is

      java.lang.AssertionError: mock://end Received message count. Expected: <0> but was: <1>
      

      Which must mean that the skipping isn’t working. Here’s the tracer output to confirm

      org.apache.camel.processor.interceptor.Tracer - ID-minhmac-local-51406-1470352938165-1-2 >>> (route3) from(direct://a) --> direct://b <<< Pattern:InOnly, Headers:{breadcrumbId=ID-minhmac-local-51406-1470352938165-1-1}, BodyType:String, Body:hello
      org.apache.camel.processor.interceptor.Tracer - ID-minhmac-local-51406-1470352938165-1-2 >>> (route4) direct://b --> mock://end <<< Pattern:InOnly, Headers:{breadcrumbId=ID-minhmac-local-51406-1470352938165-1-1}, BodyType:String, Body:hello
      

      If you remove the DirtiesContext, then both tests passes. My suspicion is that there is a bug when re-applying the MockEndpointAndSkip when the spring context is being rebuilt between tests.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              davsclaus Claus Ibsen
              Reporter:
              mtran Minh Tran

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment