You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Tadayoshi Sato (Jira)" <ji...@apache.org> on 2019/09/30 05:47:00 UTC

[jira] [Commented] (CAMEL-14020) Migrate deprecate getOut to getMessage in tests

    [ https://issues.apache.org/jira/browse/CAMEL-14020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16940659#comment-16940659 ] 

Tadayoshi Sato commented on CAMEL-14020:
----------------------------------------

I'm concerned that some tests elaborately use {{getOut()}} in order to simulate the actual component behaviours and thus changing {{getOut()}} to {{getMessage()}} may change the meanings of the tests and make them worthless.

Example:
https://github.com/apache/camel/blob/master/platforms/spring-boot/components-starter/camel-servlet-starter/src/test/java/org/apache/camel/component/servlet/springboot/test/ServletHttpMessageTest.java#L61

The problem here is that tests may still pass but since the meanings are changed they may no longer do meaningful tests.

> Migrate deprecate getOut to getMessage in tests
> -----------------------------------------------
>
>                 Key: CAMEL-14020
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14020
>             Project: Camel
>          Issue Type: Task
>          Components: tests
>         Environment: When you compile a component then deprecated WARNs is logged by the compiler. The getOut on Message should be using getMessage in the tests.
>            Reporter: Claus Ibsen
>            Priority: Major
>             Fix For: 3.x
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)