Update Microsoft.VisualStudio.QualityTools to version with symbols #15646
+1
−1
Azure Pipelines / microsoft.vstest
succeeded
Apr 9, 2026 in 15m 29s
Build #20260408.23 had test failures
Details
- Failed: 1 (0.01%)
- Passed: 18,073 (98.58%)
- Other: 259 (1.41%)
- Total: 18,333
Annotations
azure-pipelines / microsoft.vstest
Microsoft.VisualStudio.TestPlatform.CommandLine.UnitTests.Processors.PortArgumentProcessorTests.ExecutorExecuteForValidConnectionReturnsArgumentProcessorResultSuccess
Test method Microsoft.VisualStudio.TestPlatform.CommandLine.UnitTests.Processors.PortArgumentProcessorTests.ExecutorExecuteForValidConnectionReturnsArgumentProcessorResultSuccess threw exception:
Moq.MockException:
Expected invocation on the mock once, but was 0 times: td => td.ConnectToClientAndProcessRequests(2345, Mock<ITestRequestManager:41>.Object)
Performed invocations:
Mock<IDesignModeClient:9> (td):
IDesignModeClient.ConnectToClientAndProcessRequests(1234, Mock<ITestRequestManager:41>.Object)
Raw output
at Moq.Mock.Verify(Mock mock, LambdaExpression expression, Times times, String failMessage) in C:\projects\moq4\src\Moq\Mock.cs:line 337
at Moq.Mock`1.Verify(Expression`1 expression, Times times) in C:\projects\moq4\src\Moq\Mock`1.cs:line 737
at Moq.Mock`1.Verify(Expression`1 expression, Func`1 times) in C:\projects\moq4\src\Moq\Mock`1.cs:line 751
at Microsoft.VisualStudio.TestPlatform.CommandLine.UnitTests.Processors.PortArgumentProcessorTests.ExecutorExecuteForValidConnectionReturnsArgumentProcessorResultSuccess() in /_/test/vstest.console.UnitTests/Processors/PortArgumentProcessorTests.cs:line 136
at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
Loading