> looking at the example I think you might think that
> it will create a queue of stubbed responses.
Now that's just crazy talk! I write a fair number of C# classes, most
of which contain at least one property getter and setter, for example:
public SomeClass { public string Text { get; set; } }
during the course of the application running, I might instantiate
SomeClass thus:
var sc = new SomeClass { Text = "First" };
and then later on I might change the text thus:
sc.Text = "Second";
>From what you have said above Alex, we should conclude that when
running the following code:
for(var i = 0; i < 2; i++)
{
if(i == 0 && sc.Text == "First")
Console.WriteLine("First value retrieved");
if(i == 1 && sc.Text == "Second")
Console.WriteLine("Second value retrieved");
}
I would expect the following output in my Command Window
First value retrieved
Second value retrieved
but we all know that that is just nonsense .... so why would anyone
expect different behaviour from a mocking framework?
--
You received this message because you are subscribed to the Google Groups
"Rhino.Mocks" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rhinomocks?hl=.
