Mailing-List: contact dev-help@abdera.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@abdera.apache.org
Message-ID: <19636771.10391272869216460.JavaMail.jira@thor>
Date: Mon, 3 May 2010 02:46:56 -0400 (EDT)
From: "ant elder (JIRA)" <jira@apache.org>
To: abdera-dev@incubator.apache.org
Subject: [jira] Commented: (ABDERA-102) Unit tests equality assertions,
 params in wrong order.
In-Reply-To: <20365938.1202244068234.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ABDERA-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863253#action_12863253 ] 

ant elder commented on ABDERA-102:
----------------------------------

Patch applied, many thanks for the fixes Christine

> 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
>
>
> 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.