Re: [NMock2-Dev] Minor change I'd like to make

[Steve M. <Ste...@ty...>]

There may not be explicit unit tests, but the test suite itself covers
the expectation builder at 96% if you run the test suite through NCover.

-----Original Message-----
From: nmo...@li...
[mailto:nmo...@li...] On Behalf Of Mike
Capp
Sent: Thursday, August 16, 2007 8:05 AM
To: NMock2 Development Discussion
Subject: Re: [NMock2-Dev] Minor change I'd like to make

The code itself (around line 256 of Internal/ExpectationBuilder.cs) is
straightward; it's an easy fix, and would actually make things tidier
because we wouldn't need overloads.

The fact that this ~300-line class has no unit tests whatsoever  is a
little embarrassing...

M.

On 16/08/07, Steve Mitcham <Ste...@ty...> wrote:
> There was some discussion a while ago on this issue.  I'm not sure
that
> it ever got entered as a bug.  I've been bit by it when dealing with
> 'out' parameters (example: With(1,2,Is.Out) fails)
>
> I think that adding the matcher to the list using the coalescing
> operator would be pretty readable
> The following example is without having a chance to look at the code
in
> question, so I hope you get the gist
>
>         expectations.Add(x as Matcher ?? Is.EqualTo(x))

------------------------------------------------------------------------
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
NMock-two-dev mailing list
NMo...@li...
https://lists.sourceforge.net/lists/listinfo/nmock-two-dev