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
We are using Typemock Isolator 5.3.1 and the newest NUnit version with VS2008 SP1.

We are using linq in a large C# project (bad decision but can't change it anymore) and some of our queries are very big (>100 code lines). We have unit tests and there is a significant performance issue when such a query gets executed as linq parses the whole thing in order to create the sql statement. This of course is a linq issue and not a typemock problem.

But typemock seems to have some impact on the performance as well. When running a test that executes said query it takes about 17s to run. When I disable typemock (VS2008 Menu -> Tools) and execute the test again it takes only 6s. It seems to me that the parsing by linq gets affected by some typemock functionality what results in an even longer execution time. As we have a number of such tests solving 10s on every one of them would reduce our build time by about 10min!

Is this a bug that you can fix? Is there a workaround? Or can I at least disable/shutdown typemock for some specific tests?
asked by srudin (1.7k points)

1 Answer

0 votes

In the latest Isolator release (5.4.5) we improved the faking algorithm's performance and memory consumption, especially for large classes. I would suggest upgrading to the latest Isolator version and timing your tests again to see if the problem persists. Please let me know if this helps.

Typemock Support
answered by doron (17.2k points)