You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Robert E. Simmons Jr. MSc. (JIRA)" <ji...@apache.org> on 2013/09/27 10:53:09 UTC
[jira] [Created] (CAMEL-6792) Camel Test Support needs a new Method
Robert E. Simmons Jr. MSc. created CAMEL-6792:
-------------------------------------------------
Summary: Camel Test Support needs a new Method
Key: CAMEL-6792
URL: https://issues.apache.org/jira/browse/CAMEL-6792
Project: Camel
Issue Type: Bug
Components: tests
Affects Versions: 2.11.1
Environment: ALL
Reporter: Robert E. Simmons Jr. MSc.
There is a problem with the CamelTestSupport class in that if you call getMockEndpoint on an endpoint that doesnt exist, it blithely returns you an endpoint connected to nothing. The problem is you end up chasing endless test failures when the fact is your endpoint is not even there. So I suggest a method I added to my subclass of CamelTestSupport which is:
protected MockEndpoint assertAndGetMockEndpoint(final String uri) {
assertNotNull(context.hasEndpoint(uri));
return getMockEndpoint(uri);
}
This method will make sure that the endpoint is there before returning it and it will make tests easier to write.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira