HashSet incorrectly reported

Bug #794115 reported by Wernight
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NUnit Framework
Fix Released
Medium
Charlie Poole
NUnit V2
Fix Released
Low
Charlie Poole

Bug Description

Sample code
-----------------

[Test]
public void SomeTest()
{
    var actual = new HashSet<string>(new[] {"foo", "bar"});
    Assert.That(actual, Is.EquivalentTo(new[] { "fo__", "bar" }));
}

Reported as
-----------------

  Expected: equivalent to < "fo__", "bar" >
  But was: <System.Collections.Generic.HashSet`1[System.String]>

Expected being reported as:
---------------------------------------

  Expected: equivalent to < "fo__", "bar" >
  But was: < "foo", "bar" >

Environment
-----------------

NUnit version 2.5.9.10348

Related branches

Changed in nunitv2:
status: New → In Progress
importance: Undecided → Low
milestone: none → 2.6.0
assignee: nobody → Charlie Poole (charlie.poole)
Changed in nunitv2:
status: In Progress → Fix Committed
Changed in nunit-3.0:
milestone: none → 2.9.6
Changed in nunit-3.0:
status: New → Triaged
importance: Undecided → Medium
Changed in nunitv2:
status: Fix Committed → Fix Released
Changed in nunit-3.0:
status: Triaged → In Progress
assignee: nobody → Charlie Poole (charlie.poole)
Changed in nunit-3.0:
status: In Progress → Fix Committed
Changed in nunit-3.0:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.