4.0.0-beta.5

Compatibility

This release changes how the parts of RevitDevTool check that they can work together (ADR 0055). Update everything together:

• RevitDevTool.TestAdapter 0.2.0 and revitdevtool_pytest 0.6.0 need this release or later. Older adapters and pytest plugins stop with a message that names the update.
• A new adapter against RevitDevTool 4.0.0-beta.4 or older shows Testing protocol version 0 is not supported. Update RevitDevTool.
• After updating, restart Revit or AutoCAD before running tests, so the host loads the new add-in.
• The MCP gateway now rejects Daemons from before this release. Update the Daemon to reconnect the tunnel.
• Test projects need MSTest 4.5.2 and TUnit 1.78.0. A test project on the old pins fails at generation.

Added

• The Daemon window, the Revit dock pane and floating window, and the AutoCAD palette show the product version (DevTools 4.0.0-beta.5).
• Version checks by protocol range for the test adapter, TestRunner, add-in, pytest, and the MCP gateway. A mismatch ends with one sentence that names both sides and the update to make.
• When the gateway rejects the Daemon, the Daemon stops reconnecting and shows "Not compatible with the gateway".

Changed

• A Daemon update to a higher major waits while an add-in of that major is waiting for its host to close. Minor updates do not wait.
• Microsoft.Testing.Platform 2.5.2, MSTest 4.5.2, TUnit 1.78.0.
• Sentry releases use the full product version, including the prerelease suffix.

Fixed

• When pytest stops before running tests (for example a missing node id), the result names the exit code and the node ids instead of "No result received from host for this test."

Full Changelog: 4.0.0-beta.4...4.0.0-beta.5