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
When we switched to .NET 3.5, our old discontinued version of Clover.NET stopped working (and it was a great product). We really need a coverage tool that is deeply integrated with Typemock.

Since your organization are obviously experts at managing execution of .NET assemblies at the byte code level (and you obviously have no problem injecting code into a running assembly), why don't you just create and market a code coverage tool?

This would really help us out.
asked by sellingerd (5.7k points)

5 Answers

0 votes
Hi sellingerd,

Thanks for the kind words. We are indeed the masters of IL.

While building our own coverage tool is a wonderful idea, it is not in our immediate plans. Lucky for you, Isolator works together with the following tools for coverage:

- NCover
- MSTest coverege. (The VS Team System coverage tool)

There are also other profilers that also include coverage tools:
- Micro Focus DevPartner
- ExactMagic's TestMatrix
- AutomatedQA AQTime

I'm sure you can find a solution with one of our partners.
answered by gilz (14.5k points)
0 votes
what about PartCover?

or any other open source coverage tool?
answered by error (6.6k points)
0 votes

We currently don't support PartCover or other open source products.
answered by gilz (14.5k points)
0 votes
Hi Gilz,

Are there plans to support partcover in future versions of Typemock?

As partcover provides us with everything we need except coverage details for typemock'ed tests.

answered by aftan (2.5k points)
0 votes

This is already in our backlog, and we intend to provide support for PartCover. I'll see if I can bump up its priority to one of our near iterations.

Typemock Support
answered by doron (17.2k points)