Skip to content

Enable MTP tests via MSBuild property #9361

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 16, 2025
Merged

Enable MTP tests via MSBuild property #9361

merged 2 commits into from
May 16, 2025

Conversation

captainsafia
Copy link
Member

I've verified that the run-debug-test loop works or me in Codespaces with this change and the one from #9261.

cc: @peterwald @Youssef1313

cc: @radical I noticed there were some reverts/re-reverts on the PR mentioned above but I think everything is back to the state introduced by the commit from the PR.

@Copilot Copilot AI review requested due to automatic review settings May 16, 2025 17:17
@github-actions github-actions bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label May 16, 2025
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Enables Microsoft Testing Platform (MTP) tests by adjusting the MSBuild property and cleaning up an outdated workaround.

  • Set <DisableTestingPlatformServerCapability> to false to allow MTP tests to run.
  • Remove legacy workaround comments for VS Code/Test Explorer.

<!-- Workaround for VSCode issues, until it's figured out and resolved. -->
<!-- This basically causes Test Explorer in VS and VS Code to use VSTest -->
<DisableTestingPlatformServerCapability>true</DisableTestingPlatformServerCapability>
<DisableTestingPlatformServerCapability>false</DisableTestingPlatformServerCapability>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the default already and can be removed safely

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was leaning towards leaving it in case we need to go back and disable this again. I like Copilot's recommendation of adding a comment as extra clarity.

@radical
Copy link
Member

radical commented May 16, 2025

Let's run an Azdo build for this too.

@radical
Copy link
Member

radical commented May 16, 2025

@radical
Copy link
Member

radical commented May 16, 2025

How does this affect test runs? Does it work on VS too?

@Youssef1313
Copy link
Member

This PR shouldn't affect command line scenarios (including CI). It only impacts IDE (both VS and DevKit)

@captainsafia
Copy link
Member Author

How does this affect test runs? Does it work on VS too?

@Youssef1313 can share more about how it affects test runs since he has more insight onto the implementation. It does work in VS. We originally disabled it because it was broken in VS Code.

Verified this works locally on macOS.

@radical radical merged commit b709ff2 into main May 16, 2025
258 checks passed
@radical radical deleted the safia/fix-mtp-test branch May 16, 2025 20:01
Viir added a commit to pine-vm/pine that referenced this pull request Jun 4, 2025
Link discussion of issues around `dotnet  test` and MTP found at dotnet/sdk#45927 and dotnet/sdk#49210

For more related discussions, see:

+ dotnet/aspire#9361
+ dotnet/aspire#8833
@github-actions github-actions bot locked and limited conversation to collaborators Jun 16, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants