abdera-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christine Koppelt (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (ABDERA-102) Unit tests equality assertions, params in wrong order.
Date Sun, 16 May 2010 17:19:41 GMT

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

Christine Koppelt resolved ABDERA-102.
--------------------------------------

    Resolution: Fixed

fixed, see svn commits

> Unit tests equality assertions, params in wrong order.
> ------------------------------------------------------
>
>                 Key: ABDERA-102
>                 URL: https://issues.apache.org/jira/browse/ABDERA-102
>             Project: Abdera
>          Issue Type: Improvement
>    Affects Versions: 0.3.0
>            Reporter: Remy Gendron
>            Priority: Trivial
>         Attachments: coreunittests.patch, oauthtests.patch, parserunittests.patch
>
>
> When using assertEquals(), the parameters should be EXPECTED then ACTUAL.
> They are currently mostly in the opposite order.
> No big deal. It just makes the assertion messages more readable/clear if the parameters
are provided in the proper order.
> Thanks,
> R.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message