You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@falcon.apache.org by "Ajay Yadav (JIRA)" <ji...@apache.org> on 2014/11/18 07:26:33 UTC

[jira] [Updated] (FALCON-807) Fix order of actual and expected expression in assert statements.

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

Ajay Yadav updated FALCON-807:
------------------------------
    Attachment: FALCON-807.patch

> Fix order of actual and expected expression in assert statements.
> -----------------------------------------------------------------
>
>                 Key: FALCON-807
>                 URL: https://issues.apache.org/jira/browse/FALCON-807
>             Project: Falcon
>          Issue Type: Improvement
>            Reporter: Ajay Yadav
>            Assignee: Ajay Yadav
>         Attachments: FALCON-807.patch
>
>
> In Assert statements like assertEquals, actual expression should be first and expected expression should be second argument. In certain files e.g. FalconCLIIT.java we have it other way round. 
> Impact of this is:
> When the test fails the error message will say something like:
> Expected -1 but was 0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)