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
0 votes
Hello,

After having upgraded from ExactMagic (Mailframe) TestRunner to their current product TestMatrix 2, NaturalMocks support is broken.

The reason: TestRunner and TestMatrix 1 used NCover to retrieve coverage data. This changed in Version 2. Now they are instrumenting all assemblies by adding trace statements. Thus e.g.

using (RecordExpectations recorder = RecorderManager.StartRecording())
{
  baseReader.Read(null, 0, 64);
  recorder.Return(0);
}

becomes
using (RecordExpectations recorder = RecorderManager.StartRecording())
{
   ExactMagicCoverageTracker._9[60]++;
   ExactMagicExecutionTrace.EnterLine(9, 0x3d);
   ExactMagicCoverageTracker._9[0x3d]++;
   baseReader.Read(null, 0, 0x40);
   ExactMagicExecutionTrace.EnterLine(9, 0x3e);
   ExactMagicCoverageTracker._9[0x3e]++;
   recorder.Return(0);
   ExactMagicExecutionTrace.EnterLine(9, 0x3f);
   ExactMagicCoverageTracker._9[0x3f]++;
}

The additional statements confuse TypeMock and should be ignored. ExactMagicExecutionTrace and ExactMagicCoverageTracker classes are inserted into any assembly for which coverage data is to be collected.

I hope you can solve the issue easily. If you require further information, please let me know.

Thanks a lot,

Philipp
asked by philipp (2.9k points)

1 Answer

0 votes
Hi Philipp and thanks a lot for your post.
We are taking care and investigating the problem.
We will be back to you as soon as the problem will be solved !
answered by menahemc (220 points)
...