Refactor Condition evaluation - #15357

Merged

nohwnd merged 1 commit into

mainfrom

dev/ygerges/refactor

Jan 13, 2026

Azure Pipelines / microsoft.vstest succeeded Jan 12, 2026 in 14m 44s

Build #20260109.2 had test failures

0 errors / 11 warnings

Details

Failed: 1 (0.01%)
Passed: 17,563 (97.46%)
Other: 456 (2.53%)
Total: 18,020

Annotations

Check failure on line 1 in Microsoft.VisualStudio.TestPlatform.CommandLine.UnitTests.Internal.ProgressIndicatorTests.StartShouldShowProgressMessage

azure-pipelines / microsoft.vstest

Microsoft.VisualStudio.TestPlatform.CommandLine.UnitTests.Internal.ProgressIndicatorTests.StartShouldShowProgressMessage

Test method Microsoft.VisualStudio.TestPlatform.CommandLine.UnitTests.Internal.ProgressIndicatorTests.StartShouldShowProgressMessage threw exception: 
Moq.MockException: 
Expected invocation on the mock once, but was 0 times: m => m.Write(".", OutputLevel.Information)

Performed invocations:

   Mock<IOutput:165> (m):

      IOutput.Write("Test run in progress.", OutputLevel.Information)

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.Internal.ProgressIndicatorTests.StartShouldShowProgressMessage() in /_/test/vstest.console.UnitTests/Internal/ProgressIndicatorTests.cs:line 52
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)

View more details on Azure Pipelines