Update to MTP

[Youssef1313]

Motivation and Context

Keep the test infra up-to-date with the latest dependencies and moving away from VSTest to the newer Microsoft.Testing.Platform.

How Has This Been Tested?

Manually running tests locally (still not working, that's why it's draft)

Breaking Changes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Infrastructure and CI

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

[Youssef1313]

@stephentoub This hopefully should be green.

[Youssef1313]

failed ModelContextProtocol.Tests.Transport.StdioClientTransportTests.CreateAsync_ValidProcessInvalidServer_StdErrCallbackInvoked (135ms)
  Assert.InRange() Failure: Value not in range
Range:  (1 - 2147483647)
Actual: 0
  from /home/runner/work/csharp-sdk/csharp-sdk/artifacts/bin/ModelContextProtocol.Tests/Debug/net472/ModelContextProtocol.Tests.exe (Mono 6.8.0.105 (Debian 6.8.0.105+dfsg-3.6ubuntu2 Sun Mar 31 02:55:28 UTC 2024)|x64)
  Assert.InRange() Failure: Value not in range
  Range:  (1 - 2147483647)
  Actual: 0

Is this a flaky test?

[stephentoub]

failed ModelContextProtocol.Tests.Transport.StdioClientTransportTests.CreateAsync_ValidProcessInvalidServer_StdErrCallbackInvoked (135ms)
  Assert.InRange() Failure: Value not in range
Range:  (1 - 2147483647)
Actual: 0
  from /home/runner/work/csharp-sdk/csharp-sdk/artifacts/bin/ModelContextProtocol.Tests/Debug/net472/ModelContextProtocol.Tests.exe (Mono 6.8.0.105 (Debian 6.8.0.105+dfsg-3.6ubuntu2 Sun Mar 31 02:55:28 UTC 2024)|x64)
  Assert.InRange() Failure: Value not in range
  Range:  (1 - 2147483647)
  Actual: 0

Is this a flaky test?

Probably

[Youssef1313]

@stephentoub Can you please restart the failing jobs again? Looks like some flakiness.
Note: I ran this in my fork and it's green already Youssef1313#2

[eiriktsarpalis]

@Youssef1313 done

[eiriktsarpalis]

Thanks!

[eiriktsarpalis]

Hi @Youssef1313, we're getting reports of dotnet test failing after this update. I was able to repro this locally with the following error message:

The following exception occurred when running the test module with RunCommand 'C:\Users\eitsarpa\devel\mcp\csharp-sdk\artifacts\bin\ModelContextProtocol.Tests\net10.0\ModelContextProtocol.Tests.exe' and RunArguments '  --results-directory C:\Users\eitsarpa\devel\mcp\csharp-sdk\artifacts\TestResults\ --report-trx --report-trx-filename ModelContextProtocol.Tests.net10.0.Windows_NT.trx':

System.ComponentModel.Win32Exception (2): An error occurred trying to start process 'C:\Users\eitsarpa\devel\mcp\csharp-sdk\artifacts\bin\ModelContextProtocol.Tests\net10.0\ModelContextProtocol.Tests.exe' with working directory 'C:\Users\eitsarpa\devel\mcp\csharp-sdk'. The system cannot find the file specified.
   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at Microsoft.DotNet.Cli.Commands.Test.TestApplication.RunAsync()
   at Microsoft.DotNet.Cli.Commands.Test.TestApplication.RunAsync()
   at Microsoft.DotNet.Cli.Commands.Test.TestApplicationActionQueue.Read(BuildOptions buildOptions, TestOptions testOptions, TerminalTestReporter output, Action`1 onHelpRequested)