nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Ah... a further comment however: CollectionAssert was intended to be "frozen"
with all new abilities added through the Assert.That interface. In
addition, it is
expected to have the same API as the Microsoft CollectionAssert. So while we
will accept this feature, it might be implemented only as a constraint....

  Assert.That(result.DisplayStrings(), ContainsValue(displayString));

Charlie

On Tue, May 10, 2011 at 6:03 PM, Rechenelf <780607@xxxxxxxxxxxxxxxxxx> wrote:
> Public bug reported:
>
> It would be nice to have two other methods for CollectionAssert
>
> CollectionAssert.ContainsValue(result.DisplayStrings, displayString);
> instead of my current implementation
> Assert.IsTrue(result.DisplayStrings.ContainsValue(displayString));
>
> also:
> CollectionAssert.ContainsKey
>
> where result.DisplayStrings is a IDictionary
>
> ** Affects: nunit-3.0
>     Importance: Undecided
>         Status: New
>
>
> ** Tags: dictionary feature
>
> --
> You received this bug notification because you are subscribed to NUnit
> Extended Testing Platform.
> https://bugs.launchpad.net/bugs/780607
>
> Title:
>  CollectionAssert for Dictionary
>

-- 
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.
https://bugs.launchpad.net/bugs/780607

Title:
  CollectionAssert for Dictionary

Status in NUnit Test Framework:
  Triaged

Bug description:
  It would be nice to have two other methods for CollectionAssert

  CollectionAssert.ContainsValue(result.DisplayStrings, displayString);
  instead of my current implementation
  Assert.IsTrue(result.DisplayStrings.ContainsValue(displayString));

  also:
  CollectionAssert.ContainsKey

  where result.DisplayStrings is a IDictionary