Hard to beat https://github.com/Moq/moq4/wiki/Quickstart
If that's not clear enough, I'd call that a doc bug...
EDIT: In response to your clarification...
For each mocked method Setup
you perform, you get to indicate things like:
- constraints on inputs
- the value for / way in which the return value (if there is one) is to be derived
The .Callback
mechanism says "I can't describe it right now, but when a call shaped like this happens, call me back and I'll do what needs to be done". As part of the same fluent call chain, you get to control the result to return (if any) via .Returns
". In the QS examples, an example is that they make the value being returned increase each time.
In general, you won't need a mechanism like this very often (xUnit Test Patterns have terms for antipatterns of the ilk Conditional Logic In Tests), and if there's any simpler or built-in way to establish what you need, it should be used in preference.
Part 3 of 4 in Justin Etheredge's Moq series covers it, and there's another example of callbacks here
A simple example of a callback can be found at Using Callbacks with Moq post.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…