Current status of sequences in Moq

[Brian J. Cardiff]

I want to clarify a bit what I've been thinking and doing for this.

My intention was to improve mock in order to support different kind of extensions with minimum impact on the core. Many of you have different thought on what a nice api and behavior would be for sequences. Some only regarding successive returns of a methods, others about interaction of many mocks.

What I tried was to add a .When(Func<bool>) at the beginning, before the setup. This condition rules when the following expectation applies. This had some impact with the default override behavior, but backward compatibility is maintained.

Using that simple, but powerfull extension some of the scenarios you wanted were implemented. They are not at trunk yet. Some pending discussion are pending.

If you want a preview of the current supported samples in branch /branches/private/bcardiff/ConditionalSetups/ browse the follwing samples

* http://code.google.com/p/moq/source/browse/branches/private/bcardiff/ConditionalSetups/UnitTests/ReturnSequenceHelperFixture.cs

* http://code.google.com/p/moq/source/browse/branches/private/bcardiff/ConditionalSetups/UnitTests/MockSequenceFixture.cs

Also, there are some pending issues that will imply some code, but I think the main work is already done.

* Show where in the sequence the trace stoped. To improve error reporting. Similar to .VerifyAll()

* Support all overloads Func<...>, Action<...>

* Support properties, not only methods.

Brian J. Cardiff
bcardiff(?)gmail.com
.

[Daniel Cazzulino]

I like the senquencing stuff Brian! Great work and very nice API :)

One minor thing is why we need to use SetupSequentials instead of making it implicit by enabling multiple calls to Returns directly...

/kzu

--
Daniel Cazzulino | Developer Lead | XML MVP | Clarius Consulting | +1 425.329.3471

--
Post: moq...@googlegroups.com
Unsubscribe: moqdisc-u...@googlegroups.com

[Brian J. Cardiff]

That maybe another way to implement it. I just need a way to define the language that allow multiple calls to Returns. Please, review how I handle this and tell me if you find a way to reuse better all the interfaces that define the language. Either for Sequence it self, or for the conditional setups (When).

We (or me) should complete basic functionality an see if it can be merged on trunk. I think is the best approach I had accomplish for the Sequence stuff.

Brian J. Cardiff
bcardiff(?)gmail.com
.