Try using either of these: mockModel.Setup(m =>m.Items).Returns(listItem); mockModel.SetupGet(m =>m.Items).Returns(listItem); The method SetupProperty is used when you want to track its value, see. Although I am not enterily sure why SetupProperty fails, as its intention is to be able to assing and retrieve the property value, it seems likely to be caused by the private get. To be clear, let's assume your property has a public set. In that case when using Setup or SetupGet, doing something like mockModel.Object.Items = new List(); would have no effect and you would still see the list with a single item. However with SetupProperty the same statement would have changed the value returned by the property.

Basically SetupProperty allows to get AND SET the value of a property and that's why I think it cannot be used with a private set. Download Mixmeister Studio 7 2.

Moq cannot mock non-virtual methods and sealed classes. While running a test using mock object, MOQ actually creates an in-memory proxy type which inherits from your 'XmlCupboardAccess' and overrides the behaviors that you have set up in the 'SetUp' method. Rso Training Courses. And as you know in C#, you can override something only if it is marked as virtual which isn't the case with Java. Java assumes every non-static method to be virtual by default. Nexus 7 Screen And Digitizer With Bezel. Another thing I believe you should consider is introducing an interface for your 'CupboardAccess' and start mocking the interface instead.