StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>You are mocking a concrete object here. Moq works best when used with an interface. Try to <a href="http://www.google.co.uk/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&ved=0CDQQFjAA&url=http://jmock.org/oopsla2004.pdf&ei=mQUpUb_1IbKN0wXqloHIBA&usg=AFQjCNG1hoMD7NunoONsaOmVDgaQYkNmFA&sig2=7bAySxnUn5GMNBCs12mjBg&bvm=bv.42768644,d.d2k" rel="nofollow">mock roles, not objects</a> (pdf). For example, introduce an interface such as <code>IObjectRegistry</code>. At present your code knows it is dealing with an ObjectRegistry, when ideally you should be able to switch your implementation out whenever you wish. Providing you have an abstraction in place. It would be ideal both for testability and programming best practices to "<em>program to an interface</em>" instead. Note interface here does not necessarily mean an interface in terms of C#/Java etc.</p> <pre><code>var registry = new Mock<IObjectRegistry>(); public class ObjectRegistry : IObjectRegistry { // Snip } </code></pre> <p>Then use this. As this is an interface, you can freely change the concrete (real/production) class and its constructor as you wish. Your tests and the rest of the system should be unaware. If the registry had one method on the interface such as <code>GetObject</code> your system should simply rely on this abstraction, not the fact it is working with an <code>ObjectRegistry</code> instance.</p> <p>Currently your code is actually creating a real instance of an <code>ObjectRegistry</code>, then stubbing/mocking the methods in question. This is not ideal in most cases.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload