TypeMock 3.7.1 works locally, but not on build server

Hi,
1. Please post how you are building on the build server (cc.net, nant, msbuild)
2. Are you using Coverage? Which one.
3. Post the actual test command
4. What test framework are you using (nunit, mbunit, vstest)

about the second issue, please see if the add-in is enabled.
Open visual studio, Choose Tools->Add In Manager and check TypeMock (both add-in and startup)

1. We are building use msbuild (Team Foundation Server)
2. We are using the built in code coverage with VS.NET 2005
3. It is failing when I try to create a mock object.

I created a generic method to handle the casting.

public static T CreateMock<T>()
{
return (T)RecorderManager.CreateMockedObject(typeof(T));
}

When I call this method from my test I get this stack trace along with the error I posted earlier.

at TypeMock.MockManager.Init(Boolean collectAllCalls)
at TypeMock.MockManager.d(Type A_0)
at TypeMock.MockManager.Mock(Type type, Constructor mockConstructors)
at TypeMock.MockManager.MockObject(Type type, Constructor mockConstructors, Object[] args)
at TypeMock.RecorderManager.CreateMockedObject(Type typeToMock)

4. We are using Microsoft's test framework: mstest/vstest

Under the Add-in Manager, the TypeMock add-in is checked and so is Startup. This appears correct.

In version 4 you can use:

RecorderManager.CreateMockedObject<T>();

Please post the msbuild section where you run the tests.

We are using the default test targets that are part of a default Team Foundation build script. The build includes the build targets from:

C:Program FilesMSBuildMicrosoftVisualStudio8.0TeamBuildMicrosoft.TeamFoundation.Build.targets

It runs CoreTest which calls RunTestWithConfiguration which calls into some custom Team Foundation server tasks (TestToolsTask)

<Target Name="CoreTest"
Condition=" '$(RunTest)'=='true' "
DependsOnTargets="$(CoreTestDependsOn)" >

<MakeDir
Directories="$(TestResultsRoot)"
Condition="!Exists('$(TestResultsRoot)')" />

<MSBuild
Projects="$(MSBuildProjectFile)"
Targets="RunTestWithConfiguration"
Properties="BuildNumber=$(BuildNumber);Platform=%(ConfigurationToBuild.PlatformToBuild);Flavor=%(ConfigurationToBuild.FlavorToBuild);IsDesktopBuild=$(IsDesktopBuild)" />
</Target>


<Target Name="RunTestWithConfiguration" >

<TeamBuildMessage
Tag="Configuration"
Condition=" '$(IsDesktopBuild)'!='true' "
Value="$(Flavor)" />

<TeamBuildMessage
Tag="Platform"
Condition=" '$(IsDesktopBuild)'!='true' "
Value="$(Platform)" />

<!-- SearchPathRoot for not Any CPU -->
<CreateProperty
Condition=" '$(Platform)'!='Any CPU' "
Value="$(BinariesRoot)$(Platform)$(Flavor)" >
<Output TaskParameter="Value" PropertyName="SearchPathRoot" />
</CreateProperty>

<!-- SearchPathRoot for Any CPU -->
<CreateProperty
Condition=" '$(Platform)'=='Any CPU' "
Value="$(BinariesRoot)$(Flavor)" >
<Output TaskParameter="Value" PropertyName="SearchPathRoot" />
</CreateProperty>

<!-- Test task for the end-to-end build -->
<TestToolsTask
Condition=" '$(IsDesktopBuild)'!='true' and '%(MetaDataFile.Identity)'!=''"
BuildFlavor="$(Flavor)"
Platform="$(Platform)"
PublishServer="$(TeamFoundationServerUrl)"
PublishBuild="$(BuildNumber)"
SearchPathRoot="$(SearchPathRoot)"
PathToResultsFilesRoot="$(TestResultsRoot)"
MetaDataFile="%(MetaDataFile.Identity)"
RunConfigFile="$(RunConfigFile)"
TestLists="%(MetaDataFile.TestList)"
TeamProject="$(TeamProject)"
ContinueOnError="true" />

<!-- Test task for the desktop build -->
<TestToolsTask
Condition=" '$(IsDesktopBuild)'!='false' and '%(MetaDataFile.Identity)'!=''"
SearchPathRoot="$(SearchPathRoot)"
PathToResultsFilesRoot="$(TestResultsRoot)"
MetaDataFile="%(MetaDataFile.Identity)"
RunConfigFile="$(RunConfigFile)"
TestLists="%(MetaDataFile.TestList)"
ContinueOnError="true" />

</Target>

I'm glad that you now included generic methods to help with casting in v4, but I needed that back in 3.7 :)

Did you add the BeforeTest/AfterTest target?
(see Integrating with Team Foundation Server)

Overriding the BeforeTest and AfterTest targets in the TFS build script worked!

I don't understand why I don't have to do that when I'm running my tests locally. That is very confusing.

Hi
When you run the tests locally through Visual Studio TypeMock is enabled
automatically by the TypeMock Add in. (see Tools menu -> Disable TypeMock)
For the full details how to run tests with TypeMock
See Running TypeMock in the documentation