RevitDevTool.TestAdapter 0.1.2

RevitDevTool.TestAdapter

Microsoft Testing Platform adapter that runs tests inside a CAD/BIM host. Requires RevitDevTool.

Supports NUnit (default), TUnit, and MSTest. Pin the framework in the test project — the adapter does not pull it. It depends on Microsoft.Testing.Platform.MSBuild 2.4.1; do not add or override it. TUnit 1.72.10 and Microsoft.Testing.Platform 2.4.1 are a pair — pin both. MSTest is pinned at 4.4.1 with the same MTP version.

All three work with every host below. Set HostName and HostVersion to the version you run. Include a compile-only host API package (discovery needs it). Do not copy host API DLLs next to the test output.

HostName: Revit, AutoCad, Civil3D, Plant3D, AcadArch, AcadMech, AcadElec, AcadMep, AcadMap3D.

Default engine is NUnit. Set TestingFramework to tunit or mstest. Do not use .runsettings.

NUnit (default)

<PropertyGroup>
  <HostName>Revit</HostName>
  <HostVersion>2025</HostVersion>
  <ForceLaunch>false</ForceLaunch>
  <PerTestTimeout>60</PerTestTimeout>
  <LaunchTimeout>180</LaunchTimeout>
</PropertyGroup>
<ItemGroup>
  <PackageReference Include="RevitDevTool.TestAdapter" Version="0.1.2" />
  <PackageReference Include="NUnit" Version="5.0.0" />
  <PackageReference Include="Revit_All_Main_Versions_API_x64" Version="2025.0.*"
    IncludeAssets="build; compile" PrivateAssets="All" />
</ItemGroup>

TUnit

<PropertyGroup>
  <HostName>Revit</HostName>
  <HostVersion>2025</HostVersion>
  <ForceLaunch>false</ForceLaunch>
  <PerTestTimeout>60</PerTestTimeout>
  <LaunchTimeout>180</LaunchTimeout>
  <TestingFramework>tunit</TestingFramework>
</PropertyGroup>
<ItemGroup>
  <PackageReference Include="RevitDevTool.TestAdapter" Version="0.1.2" />
  <PackageReference Include="TUnit" Version="1.72.10" />
  <PackageReference Include="Revit_All_Main_Versions_API_x64" Version="2025.0.*"
    IncludeAssets="build; compile" PrivateAssets="All" />
</ItemGroup>

MSTest

Use Sdk="MSTest.Sdk" (it sets EnableMSTestRunner). Microsoft.NET.Sdk with <EnableMSTestRunner>true</EnableMSTestRunner> is the other accepted shape. Without that runner, MSTest turns Microsoft.Testing.Platform off and the testhost entry point is not generated.

Pin the SDK at 4.4.1, either on the Sdk attribute or in global.json (msbuild-sdks). The in-host closure is MSTest.TestFramework 4.4.1 plus Microsoft.Testing.Platform 2.4.1. A different MSTest version fails generation.

<Project Sdk="MSTest.Sdk/4.4.1">
  <PropertyGroup>
    <HostName>Revit</HostName>
    <HostVersion>2025</HostVersion>
    <ForceLaunch>false</ForceLaunch>
    <PerTestTimeout>60</PerTestTimeout>
    <LaunchTimeout>180</LaunchTimeout>
    <TestingFramework>mstest</TestingFramework>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="RevitDevTool.TestAdapter" Version="0.1.2" />
    <PackageReference Include="Revit_All_Main_Versions_API_x64" Version="2025.0.*"
      IncludeAssets="build; compile" PrivateAssets="All" />
  </ItemGroup>
</Project>

Selecting one test also runs its [DependsOn] prerequisites (method and class, transitive). [DependsOn] only orders tests that are already in the run; the adapter and the in-host session both add those prerequisites before the run.

Targeting net48 (Revit / AutoCAD 2024 and older)

Do not add <RuntimeIdentifier> on net8 / net10. The package flattens testhost output (AppendRuntimeIdentifierToOutputPath=false). Restore cannot read a RID from this package (NETSDK1047 if the props set one). On net8 / net10 a project-level RID also nests testhost output under win-x64, which Test Explorer can bind instead of the current build. On net48, set win-x64 only when the SDK requires it for an x64 executable.

Central Polyfill

NUnit and MSTest do not need Polyfill. net48 TUnit gets [ModuleInitializer] from this package.

If the repo uses central package management with a GlobalPackageReference named Polyfill (typical in Revit add-in trees), remove it on a net48 TUnit project or TUnit restore can duplicate the package (NU1504) and a second declaration can collide (CS0436):

<GlobalPackageReference Remove="Polyfill" />

Leave NetFxModuleInitializer unset. The package compiles ModuleInitializerAttribute into net4x TUnit projects and already skips when Polyfill or a compile item named ModuleInitializerAttribute.cs is present.

Set it to false when that skip cannot see your type (otherwise CS0436): the attribute lives in a differently named file, you use PolySharp / a polyfill package not named Polyfill, or you restore Polyfill yourself and set EnableTUnitPolyfills=true.

<NetFxModuleInitializer>false</NetFxModuleInitializer>

NUnit, MSTest, and net8.0-windows / net10.0-windows ignore NetFxModuleInitializer.

dotnet test needs this in global.json. Put it on the repo root when the whole repo's dotnet test surface is MTP. One VSTest leftover: keep MTP at root and put "runner": "VSTest" (plus sdk) in that project's folder. Scope MTP next to the test project only when many non-MTP tests share the tree. An MSTest project that uses Sdk="MSTest.Sdk" without a version on the attribute also pins the SDK here.

{
  "sdk": { "version": "10.0.0", "rollForward": "latestMinor" },
  "test": { "runner": "Microsoft.Testing.Platform" },
  "msbuild-sdks": { "MSTest.Sdk": "4.4.1" }
}

dotnet test --project path/to/Host.Tests/Host.Tests.csproj -c Debug --filter MethodName

--filter is a test method name or substring. Run dotnet test from a directory covered by that global.json (repo root when the runner is there). A VSTest override is cwd-only: cd into that folder before dotnet test.

The package passes --output Detailed and --show-stdout All, so Console.WriteLine from a passing test is on that test's standard output. Normal output expands failures only.