TypeMock.NET Community

RE: Isolator Tracer empty

ohad — Sun, 08 Nov 2009 15:47:41 GMT

Hi,

Thanks for the info.
Can it be that the TestDriven process is running with different security privileges than the tracer?
_________________
Regards

Ohad,
TypeMock Support Group

Topic Replies: 5

RE: Failed to mock Unity 1.2 Resolve calls with 5.3.5

Elisha — Sun, 08 Nov 2009 10:24:28 GMT

Hi,

We plan to fix this bug in the near future, I can't give yet exact time but it's a high priority bug.

Are you using in the production code in the concrete UnityContainer or IUnityContainer? If you use the interface, it's possibly that the issue will be solved using fakes of IUnityContainer;

This bug is caused in specific cases where method is overloaded with generic overload, with different return types on which generic constraint defined.

Can you please post the code of ILoginService? I would like to reproduce it here and verify it's caused by the same reason.

Regards,
Elisha
Typemock Support

Topic Replies: 3

RE: Failed to mock Unity 1.2 Resolve calls with 5.3.5

marchy — Sat, 07 Nov 2009 23:13:24 GMT

Are there any updates to this problem yet?
This is a critical deal-breaker for any applications that want to use Unity for Dependency Injection which is more and more commonplace.

Any applications that make service calls likely have local versions of the service classes that are used when running the application during development, and dependency injection is a really common pattern for solving this problem in a clean way.

Any comments on the plans for getting this working? Also if you could shed any light on the underlying issues it would be kindly appreciated. This so far prevents us from adopting TypeMock as a feasible mocking framework for our organization, which is sad because there are certainly a lot of upsides we were looking forward to.

Another variation that doesn't work:

Code:

ILoginService loginService = Isolate.Fake.Instance<ILoginService>();
Container.RegisterInstance( loginService );
Isolate.WhenCalled( () => loginService.Authenticate( validCredentials )).WillReturn( true );

after resolving the mocked instance the matchers that were set up do not match:

Code:

ILoginService loginService = Container.Resolve<ILoginService>()
bool thisShouldReturnTrueButReturnsFalse = loginService.Authenticate( validCredentials );

Topic Replies: 3

RE: An exception when combining Typemock with PostSharp

Elisha — Sat, 07 Nov 2009 18:54:53 GMT

Hi,

Thanks for the detailed report, we'll try to reproduce it here and investigate it.

Regards,
Elisha
Typemock Support

Topic Replies: 1

An exception when combining Typemock with PostSharp

mod — Sat, 07 Nov 2009 18:28:20 GMT

hi

when i trying to apply TypeMock Isolator on code that uses PostSharp, it throws the following exception:

Quote:

Test method PostSharpTypeMockTest.Test.ProgramTest.DoSomethingTest threw exception: System.TypeInitializationException: The type initializer for '<>AspectsImplementationDetails_1'� threw an exception. ---> System.NullReferenceException: Object reference not set to an instance of an object..

Stack Trace:

Quote:

b2.a(Object A_0)
ax.a(Object A_0)
ax.a(String A_0, Object A_1)
TypeMock.MockManager.a(String A_0, String A_1, Object A_2, Object A_3, Boolean A_4)
TypeMock.InternalMockManager.isMocked(Object that, String typeName, String methodName, Object methodParameters, Boolean isInjected)
AspectsImplementationDetails_1..cctor()
PostSharpTypeMockTest.Program.DoSomething()
PostSharpTypeMockTest.Test.ProgramTest.DoSomethingTest()
TypeMock.MockManager.a(String A_0, String A_1, Object A_2, Object A_3, Boolean A_4, Object[] A_5)
TypeMock.InternalMockManager.getReturn(Object that, String typeName, String methodName, Object methodParameters, Boolean isInjected)
PostSharpTypeMockTest.Test.ProgramTest.DoSomethingTest()

Used environment:
Windows 7 RC x64
Microsoft Visual Studio Team System 2008
PostSharp 1.5.6.629 x64
Typemock Isolator 5.43 x64

the same behavior also seen on the following environment:
Windows XP SP3 x64
Microsoft Visual Studio 2008 Developer Edition
PostSharp 1.5.6.629 x86
Typemock Isolator 5.43 x86

Sample C# Executable Code:

Code:

[Serializable]
public class TestAspect : OnMethodBoundaryAspect
{

}

public class Program
{
static void Main(string[] args)
{
Console.WriteLine("Main");
DoSomething();
}

[TestAspect]
public static void DoSomething()
{
Console.WriteLine("DoSomething");
Do2();
}

public static void Do2()
{
Console.WriteLine("Do2");
}
}

Sample C# Test Code:

Code:

[TestMethod()]
[Isolated]
public void DoSomethingTest()
{
Isolate.WhenCalled(() => Program.Do2())
.DoInstead(
x => System.Console.WriteLine("Do2 Mocked")
);
Program.DoSomething();
}

when i removing the [TestAspect] attribute, the test passing.

Topic Replies: 1

RE: How to mock XmlNode

Elisha — Fri, 06 Nov 2009 17:11:10 GMT

Hi,

You can handle it using indexer faking:

Code:

Isolate.WhenCalled(() => doc.ChildNodes[1]).WillReturn(fakeElement);

Regards,
Elisha
Typemock Support

Topic Replies: 3

RE: How to mock XmlNode

mohit.vashishtha — Fri, 06 Nov 2009 15:58:31 GMT

Thanks for reply...

Actualy i am still stuggling with same issue. When i tried to create the mock object named as "root" from the XmlDocument then it is throwing object reference error. Befor the foeeach loop there is lines of code as:

Code:

Hashtable languageTable = new Hashtable();
string cultureName = currentInfo.Name;
XmlDocument doc = new XmlDocument();
XmlTextReader myReader = new XmlTextReader(xmlUrl);
myReader.XmlResolver = myResolver;
doc.Load(myReader);
XmlNode root = doc.ChildNodes[1];
foreach (XmlNode node in root.ChildNodes) \\\Here it breaks
{
if (string.Compare(node.Name, "token", true) != 0) continue;

I am able to mock the "XmlDocument" and its load call. But when its trying to fetch the first child node, it returns me null object.

Please share some inputs that how can i mock the first element of the XML document as XMLNode("root").

Thanks
Mohit

Topic Replies: 3

RE: Isolator 5.4.3 "productivity" puts VS in loop

ramnefors — Fri, 06 Nov 2009 15:18:50 GMT

OK, that worked.

Thanks

Mats

Topic Replies: 4

RE: Isolator 5.4.3 "productivity" puts VS in loop

Elisha — Fri, 06 Nov 2009 13:48:54 GMT

Hi,

As a workaround, search for the file TypeMock.Productivity.AddIn (It's located in VS addins directory) and rename to it TypeMock.Productivity.AddIn_. It will prevent Visual Studio from loading the addin.

Let me know if it helps.

Regards,
Elisha
Typemock Support

Topic Replies: 4

RE: Isolator 5.4.3 "productivity" puts VS in loop

ramnefors — Fri, 06 Nov 2009 12:59:33 GMT

Hi,

The problem is that the StartUp checkbox is greyed out so I can not uncheck it.

The isolator productivity checkbox (leftmost) I have already unchecked otherwise I would not be able to use VS at all.

But with the StartUp checkbox disabled I have to disable "productivity" every time I start VS.

How can I uncheck StartUp?

Mats

Topic Replies: 4

RE: Two "Quickstart" entries in VS Help menu

Elisha — Fri, 06 Nov 2009 12:28:57 GMT

Hi Mats,

It seems like a bug We're trying to reproduce it and fix it. Thanks for letting us know!

Regards,
Elisha
Typemock Support

Topic Replies: 1

RE: Isolator 5.4.3 "productivity" puts VS in loop

Elisha — Fri, 06 Nov 2009 12:27:01 GMT

Hi Mats,

Thanks for reporting, we received similar report about IntelliTest and VB, it's a bug.

I recommend in this case to disable the productivity addin from starting with Visual Studio: Tools -> Add-ins manager -> uncheck Issolator Productivity checkbox and Startup checkbox. It will unload the productivity features but will let you use the all other new features of Isolator.

Please let me know if it helps.

Regards,
Elisha
Typemock Support

Topic Replies: 4

Two "Quickstart" entries in VS Help menu

ramnefors — Fri, 06 Nov 2009 08:16:33 GMT

Hi,

After upgrading to 5.4.3 I now have two entries for "Typemock isolator quickstart" in the help menu.

Mats

Topic Replies: 1

Isolator 5.4.3 "productivity" puts VS in loop

ramnefors — Fri, 06 Nov 2009 08:02:38 GMT

Hi,

Yesterday I upgraded to 5.4.3. It seem that Typemock Productivity (TP) is making Visual Studio behave in a very unproductive way

If I try to type in a variable name at the start of a line (VB) after the first letter Typemock immediately adds "()" , giving for instance "a() or _p()". if I try to backspace over it Typemock adds the paranthesis again so we are stuck in an infinite loop.

If I use AddIn Manager to switch off TP I can continue to type normally.

Unfortunately there seem to be no way of preventing TP to start in the first place so I have to use AddIn manager to disable TP everytime I start Visual Studio. I would urgently want a fix for this or I will have to downgrade to the previous version.

I am running VS2008 SP1 programming in VB with the test code in C#. This problem is in the VB code.

Mats

Topic Replies: 4

RE: IntelliTest breaks intellisense in Visual Basic 2008

halstein — Thu, 05 Nov 2009 22:38:39 GMT

The workaround worked. Disabling TypeMock Productivity got the intellisense in Visual Studio working again for Visual Basic. Sadly, 5.4.3 still doesn�t work with Gallio on x64 Windows, so it is back to 5.3.1 anyway.

Topic Replies: 3