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're investigating a performance issue in our unit tests.

The issue is that NUnit [Repeat] attribute makes unit tests run 100 times slower than using a for loop inside the test. The time is visibly not from the SetUp and there is a clear overhead running any test case. ANTS profiler seem to indicate that all the time is taken by the assembly loading a reflection calls to check attributes. Sadly it's not visible if TypeMock if doing those calls to for its [Isolate] attributes or if it's something else.

I was wondering if you had some suggestion or insight on such issues.
asked by Wernight (840 points)

2 Answers

0 votes
This doesn't seem to affect some much all unit tests which makes it less likely to be directly due to TypeMock.
answered by Wernight (840 points)
0 votes
Sorry, seems mostly something in our code.
answered by Wernight (840 points)
...