What is your test trying to achieve? What behaviour or state are you verifying? Specifically, are you verifying that the collaborator (data) is having its ListCount method called (interaction based testing), or do you just want to make ListCount return a canned value to drive the class under test while verifying the result elsewhere (traditional … Read more
Try the “OutRef” option. It accepts a params object[] that defines the result for each out parameter. Since you’ve only got one, you only need one result. Here’s a quick mock-up of what I tried that should work in your situation: var foo = MockRepository.GenerateStub<IFoo>(); var viewModel = new LoginViewModel(); User temp; foo.Stub(f => f.IsLoginValid(viewModel, … Read more
you should use a mock when you are going to verify that something happened on the object, like a method was called. You should use a stub when you just want the object to be involved in the test to return a value but it is not the thing you are testing. A stub which … Read more
You can specify the 2nd argument as Arg<T>.Is.Anything, then the actual value gets ignored. However note that using this you need to use Arg for all arguments. Which means you need to use on the first argument: Arg<int>.Is.Equal(123).
You can provide an implementation for a method with the Do() handler: Func<TypeX,TypeY,TypeZ,TypeZ> returnThird = (x,y,z) => z; mock.Expect(x => x.Method(null, null, null)).IgnoreArguments().Do(returnThird); Note that TypeZ appears twice because it is both an input argument type and the return type.
Would the static IdentityResult.Success property work? http://msdn.microsoft.com/en-us/library/microsoft.aspnet.identity.identityresult.success(v=vs.108).aspx Edit: To add some more detail, it seems what you want to do is get your mocked CreateAsync to return an IdentityResult where Suceeded is true. For that I would just return IdentityResult.Success from your mock. There’s shouldn’t be a need to mock the IdentityResult itself. Example: How … Read more
An InMemory provider is included in EF7 (pre-release). You can use either the NuGet package, or read about it in the EF repo on GitHub (view source).
I usually do exactly what you ended up doing in your test. When writing my tests I assume that the .Net library classes work correctly and don’t contain bugs, so I can use them in the tests. When I need a test list, collection, queryable, dictionary, etc. I just create the real thing and populate … Read more
Is it possible to mock a static method using Rhino.Mocks No, it is not possible. TypeMock can do this because it utilizes the CLR profiler to intercept and redirect calls. RhinoMocks, NMock, and Moq cannot do this because these libraries are simpler; they don’t use the CLR profiler APIs. They are simpler in that they … Read more
You could use the WhenCalled method like this: myStub .Stub(_ => _.Create(Arg<Invoice>.Is.Anything)) .Return(null) // will be ignored but still the API requires it .WhenCalled(_ => { var invoice = (Invoice)_.Arguments[0]; invoice.Id = 100; _.ReturnValue = invoice; }); and then you can create your stub as such: Invoice invoice = new Invoice { Id = 5 … Read more