Merge pull request #1075 from stakx/inner-mock-setups

Don't require inner mock setups to be matched

CHANGELOG.md

@@ -20,6 +20,7 @@ The format is loosely based on [Keep a Changelog](http://keepachangelog.com/en/1
 
 * Setup not triggered due to VB.NET transparently inserting superfluous type conversions into a setup expression (@InteXX, #1067)
 * Nested mocks created by `Mock.Of<T>()` no longer have their properties stubbed since version 4.14.0 (@vruss, @1071)
+* `Verify` fails for recursive setups not explicitly marked as `Verifiable` (@killergege, #1073)
 
 
 ## 4.14.6 (2020-09-30)

src/Moq/InnerMockSetup.cs

@@ -35,5 +35,11 @@ protected override void ResetCore()
 		{
 			this.InnerMock.MutableSetups.Reset();
 		}
+
+		protected override bool TryVerifySelf(out MockException error)
+		{
+			error = null;
+			return true;
+		}
 	}
 }

tests/Moq.Tests/Regressions/IssueReportsFixture.cs

@@ -3488,6 +3488,30 @@ public void Property_set_up_with_Mock_Of_is_automatically_stubbed__manual_inner_
 
 		#endregion
 
+		#region 1073
+
+		public class Issue1073
+		{
+			[Fact]
+			public void Test()
+			{
+				var mock = new Mock<IClassA>();
+				mock.Setup(x => x.Items.Count).Returns(1);  // not verifiable, but won't be invoked
+				mock.Setup(x => x.Method()).Verifiable();   // verifiable, and will be invoked
+
+				mock.Object.Method();
+
+				mock.Verify();
+			}
+			public interface IClassA
+			{
+				public IList<string> Items { get; set; }
+				public void Method();
+			}
+		}
+
+		#endregion
+
 		// Old @ Google Code
 
 		#region #47