camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-6792) Camel Test Support needs a new Method
Date Sat, 28 Sep 2013 08:41:03 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen updated CAMEL-6792:
-------------------------------

    Patch Info:   (was: Patch Available)
    
> Camel Test Support needs a new Method
> -------------------------------------
>
>                 Key: CAMEL-6792
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6792
>             Project: Camel
>          Issue Type: Wish
>          Components: camel-test
>    Affects Versions: 2.11.1
>         Environment: ALL
>            Reporter: Robert E. Simmons Jr. MSc.
>            Priority: Minor
>
> 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

Mime
View raw message