My company recently renewed our maintenance license and so I updated Isolator from version 6.1.2.0 to version 6.2.5.0. It broke a test that fakes a LINQ-to-SQL data context. The problem seems to be faking a Table<T>, since the simple test below throws an exception. I have been unable to work around the issue.
[TestMethod]
public void FakeTable()
{
var fakeTable = Isolate.Fake.Instance<System.Data.Linq.Table<object>>();
fakeTable.DeleteAllOnSubmit(new object[0]);
}
Full exception details:
Test method MySolution.MyTests.FakeTable threw exception:
System.NullReferenceException: Object reference not set to an instance of an object.
at jd.c()
at fh.b(MethodBase A_0, Object[] A_1, TypeParams A_2)
at ip.a(String A_0, Object[] A_1, Object A_2, Object A_3, String A_4, Type A_5, MethodBase A_6)
at do.a(String A_0, Object A_1, MethodBase A_2, Object[] A_3, Object A_4, String A_5, ip A_6)
at do.a(Object A_0, String A_1, String A_2, MethodBase A_3, Object[] A_4, Object A_5)
at System.Data.Linq.Table`1.DeleteAllOnSubmit(IEnumerable`1 entities)
at TestCoreInterface.ServicesTests.FakeTable() in ServicesTests.cs: line 363
at TypeMock.MockManager.a(String A_0, String A_1, Object A_2, Object A_3, Boolean A_4, Boolean A_5, Object[] A_6)
at TypeMock.InternalMockManager.getReturn(Object that, String typeName, String methodName, Object methodParameters, Boolean isInjected, Boolean isInterceptedType)
at MySolution.MyTests.FakeTable() in MyTests.cs: line 361
Thanks!