This project is read-only.
Note on 2012 usage: This documentation is for TFS2010, as of Aug 2012 the activities shipped by Typemock in V 7.x only support TFS 2010. If you need to integrate with TFS 2012 build see the blog post
Note  of official Typemock support: With the release of Typemock Isolator 6.2 there is direct support for TFS 2010 in the package so this activity does not have to be used, though this activity can still be used if required.  For more details see
TeamBuild 2010 Activity to run Typemock Isolator based tests

This activity is designed to allow Typemock Isolator based tests to be run inside a TFS 2010 Team Build. This activity is required because you have start Isolator’s mocking interceptor before you run any tests that use Typemock (and stop it afterwards). If you are running in the Visual Studio IDE this is all done automatically, but is not done as part of an MSBuild Team Build Process by default.

In prior versions of TFS (2005/2008) a solution was provide by Typemock in the form a pair of MSBUILD Tasks to start and stop the mocking process which you wired into your team MSBuild definition file.

The problem with Team Build 2010 is that you no longer get this single MSBUILD file to manage the whole Team Build, it is now a XAML workflow. In the past the single MSBUILD file ran in a single process, so you could start and stop the mocking tools as you required, and be sure they were running when you needed them. Under the new workflow model each activity is its own process (and can potentially be run in parallel). So to make sure mocking intercepting is running at the right time it must be handled atomically with running MSTest. This can only currently be achieved by wrapping the call to MSTest.EXE inside Typemock’s TMOCKRUNNER.EXE.

This activity actually provides a generic external test runner that takes most of the standard parameters passed to the MSTest activity and transforms them such that they can be used by TMOCKRUNNER. Though designed for the purpose of running Typemock Isolator, there is no reason that this activity could be used for any task that requires one executable to be wrappered in another.

The source, documentation and a built activity assembly can be download from

Last edited Aug 14, 2012 at 11:29 AM by rfennell, version 7


No comments yet.