Misleading doc of CollectionAssert.AreEqual() and .AreEquivalent()

Bug #631809 reported by Marco Eckstein
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NUnit V2
Fix Released
Low
Charlie Poole

Bug Description

http://www.nunit.org/index.php?p=collectionAssert&r=2.5.7 states (my uppercase for highlighting):

"The AreEqual overloads succeed if the two collections contain the SAME objects, in the same order. AreEquivalent tests whether the collections contain the SAME objects, without regard to order."

From my understanding, something like the following note should be appended:

"Here, "same objects" does not mean reference equality but equality regarding to the default equality comparison."

Changed in nunitv2:
importance: Undecided → Low
Changed in nunitv2:
status: New → Triaged
Changed in nunitv2:
milestone: none → 2.5.8
assignee: nobody → Charlie Poole (charlie.poole)
Changed in nunitv2:
status: Triaged → 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.