chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
Welcome to Typemock Community! Here you can ask and receive answers from other community members. If you liked or disliked an answer or thread: react with an up- or downvote.
0 votes
I installed the latest version of Typemock and found that I couldn't function with it installed. Solution startup time was increased dramatically. The CPU of the devenv process was running at about 13% for 3 minutes. My normal startup time is about 1 minute. If I clicked the little shields next to a test, I couldn't use the IDE for about a minute . The CPU was again running at 13% for this process. And I could never touch any of the buttons that popped up after the shield finally displayed its options. So forget all the fancy new GUI stuff that doesn't work, I thought I would try to run some tests. We had a bunch of test failures that previously worked with version 6. I don't really have time to research all of this right now. Back to version 6 I go. Wondering if anybody else has had a bad first impression of version 7.
asked by (9.6k points)

6 Answers

0 votes
Hi,

The reported issues are very disturbing and I'd like to provide a solution as quick as possible.

VS performance - Are you working on a very large solution? Can you please let us know what addins and extensions are enabled? It is also possible to disable one of them (for example Productivity addin or Auto-Runner extension) and see if the issue still reproduces.

Broken tests - Isolator V7 has no breaking changes, if a test from V6 passed and it fails now it is a bug. Can you post a test code that reproduces this issue?

Regards,
Elisha,
Typemock Support
answered by (12k points)
0 votes
I would say it is a medium sized solution. Unfortunately I already uninstalled V7 and will not have time at the moment to play around with the things you have mentioned. When I have time I will update the post.
answered by (9.6k points)
0 votes
I also tried (for a very brief period) version 7, but immediately I noticed a considerable slowness in VS2010 (ultimate with a medium size solution). I also have ReSharper and PostSharp enabled. For now, I just switched back to version 6.2.3 wich was working fine before.
answered by (5.5k points)
0 votes
Hi,

Which version of V7 did you try? The latest version, 7.0.6, contains major performance improvement. If it still happens in your VS I'd like to check it.
answered by (12k points)
0 votes
Hi,

Which version of V7 did you try? The latest version, 7.0.6, contains major performance improvement. If it still happens in your VS I'd like to check it.


I have to admit, I do not exactly know which version I used. But I downloaded it and installed it, the same day as I posted my message. A related problem is that TypeMock is used by a shared project on different machines. As I have to update all references to TypeMock in all the test projects of my solution, I cannot commit anymore, unless all machines switch to the new TypeMock version. So, to just try out TypeMock on one machine, is not an option. Therefore, I have taken the safe road of using the excellent working version of 6.2.3.

So, the problem is that whenever we choose to switch to a different version of TypeMock, we should do so for all developers and for all projects we are working on. This is a real obstacle.
answered by (5.5k points)
0 votes
Hi,

Regarding the upgrade of Isolator version in shared project - Isolator V7 adds new support to work side by side with previous versions. This means, for example, that you can work on you machine on projects with Isolator 7.0.6, 6.1.0 and 6.0.0 on the same time. In order to work this way, all needed is to check into the source control the assemblies of old version and ensure the test projects reference that location. The required files are:
  • Typemock.dll
  • Typemock.ArrangeActAssert.dll
  • Typemock.Interceptors.dll
  • Configuration.dll

Users with V7 installed - when compiling against local installed version will execute the tests in V7, when working with project that compiles with older version will execute with the compiled version. This means that local upgrades of the version won't affect other developers that haven't upgraded yet.

Users with older version installed - can work as working, all needed is to check the installed version assemblies into the source control once.
answered by (12k points)
...