Repository navigation
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: thomhurst/TUnit
Length of output: 204
🏁 Script executed:
Repository: thomhurst/TUnit
Length of output: 5260
🌐 Web query:
MSTest 4.4.0 MSTest.TestAdapter MSTest.TestFramework Microsoft.Testing.Platform dependency💡 Result:
As of September 2, 2026, MSTest 4.4.0 is under active development and is considered a future release, with preview versions available [1][2]. The relationship between the key MSTest components and Microsoft.Testing.Platform (MTP) is defined as follows: Microsoft.Testing.Platform (MTP) Integration MTP serves as a lightweight, cross-platform alternative to VSTest, designed to be embedded directly into test projects as an executable [3][4]. MSTest provides native support for MTP through the MSTest runner [3]. When configured, this allows tests to run as standard.NET applications (e.g., via dotnet run or direct execution), removing the dependency on external runners like vstest.console [3][4]. Dependency Structure - MSTest.TestFramework: Contains the core testing framework libraries, attributes, and assertion APIs [5][6]. - MSTest.TestAdapter: Contains the logic to discover and execute tests [5][6]. - Dependency Evolution: Historically, MSTest.TestAdapter did not explicitly list MSTest.TestFramework as a NuGet dependency, as the adapter often included the framework DLLs or handled resolution internally [7]. However, modern MSTest v4 workflows encourage the use of the MSTest metapackage, which simplifies project configuration by automatically including both the framework and the adapter [7][5]. Changes in 4.4.0 (Development) The upcoming 4.4.0 release continues to refine MTP integration. A notable architectural change in 4.4.0 makes the MSTest path to Microsoft.Testing.Platform "native-only" [8]. Specifically, MSTest.TestAdapter has been updated to remove dependencies on VSTest-bridge components (e.g., Microsoft.Testing.Extensions.VSTestBridge) and instead references MTP components like Microsoft.TestPlatform.ObjectModel directly [8]. Recommendation For new projects, it is recommended to use the MSTest metapackage or the MSTest SDK to manage these dependencies automatically, as they ensure compatibility between the framework, adapter, and the chosen test platform (MTP or VSTest) [7][5][9].
Citations:
🏁 Script executed:
Repository: thomhurst/TUnit
Length of output: 1327
🏁 Script executed:
Repository: thomhurst/TUnit
Length of output: 29247
Align the MSTest dependency family before merge.
MSTest.TestAdapter4.4.0 requires several Testing Platform packages at2.4.0or later, but this file pins them to2.3.3.MSTest4.4.0 also requiresMicrosoft.Testing.Extensions.CodeCoverage18.11.0or later, while this file pins18.10.0. Update the affected package family to compatible versions.🤖 Prompt for AI Agents