SetupAllProperties doesn't setup properties that don't have a setter

[NGloreous]

This is a regression from previous behavior. I think it was introduced by the change to fix this issue:

https://code.google.com/p/moq/issues/detail?id=199&can=1&q=SetupAllProperties

If I run the following code with version 3.1.416.3 it works fine but if I run it with the latest version 4.2.1409.1722 it fails with the error:

"MockException: IGet.GetOnly invocation failed with mock behavior Strict. All invocations on the mock must have a corresponding setup."

void Main()
{
    var mock = new Mock<IGet>(MockBehavior.Strict);
    mock.SetupAllProperties();

    Console.WriteLine(mock.Object.GetOnly);
}

public interface IGet
{
    string GetOnly { get; }
}

This is blocking my team from upgrading to the latest version. Hopefully this can be fixed because this is causing over 200 unit test failures when I try to upgrade.

Thanks!

[kzu]

Any chance that you can have a shot at sending a PR with a fix?

/kzu from mobile
On Oct 9, 2014 8:46 PM, "NGloreous" notifications@github.com wrote:

This is a regression from previous behavior. I think it was introduced by
the change to fix this issue:

https://code.google.com/p/moq/issues/detail?id=199&can=1&q=SetupAllProperties

If I run the following code with version 3.1.416.3 it works fine but if I
run it with the latest version 4.2.1409.1722 it fails with the error:

"MockException: IGet.GetOnly invocation failed with mock behavior Strict.
All invocations on the mock must have a corresponding setup."

void Main()
{
var mock = new Mock(MockBehavior.Strict);
mock.SetupAllProperties();

Console.WriteLine(mock.Object.GetOnly);

}

public interface IGet
{
string GetOnly { get; }
}

This is blocking my team from upgrading to the latest version. Hopefully
this can be fixed because this is causing over 200 unit test failures when
I try to upgrade.

Thanks!

Reply to this email directly or view it on GitHub
#136.

[NGloreous]

I'll take a look this weekend and see if I can get it fixed.

[kzu]

Thanks!

/kzu from mobile
On Oct 14, 2014 12:31 PM, "NGloreous" notifications@github.com wrote:

I'll take a look this weekend and see if I can get it fixed.

Reply to this email directly or view it on GitHub
#136 (comment).

[NGloreous]

Pull request with fix submitted.