FEST

Error message when comparing Strings is not consistent between JUnit and TestNG

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: FEST-Assert 1.1
  • Fix Version/s: FEST-Assert 1.2
  • Component/s: Assert
  • Labels:
    None
  • Number of attachments :
    0

Description

If JUnit is present, FEST-Assert creates a ComparisonFailure instead of an AssertionError. In this case, the error message is formatted as follows:

A Test expected:<[Yoda]> but was:<[Luke]>

but it is expected to be:

[A Test] expected:<'Yoda'> but was:<'Luke'>

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Alex Ruiz added a comment -

I just found out that ComparisonFailure adds brackets to the expected and actual values to indicate the differences between these two values.

Show
Alex Ruiz added a comment - I just found out that ComparisonFailure adds brackets to the expected and actual values to indicate the differences between these two values.
Hide
Permalink
Alex Ruiz added a comment -

The expected error message when JUnit is present should be:

[A Test] expected:<'[Yoda]'> but was:<'[Luke]'>
Show
Alex Ruiz added a comment - The expected error message when JUnit is present should be: 
[A Test] expected:<'[Yoda]'> but was:<'[Luke]'>

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.