From fb0a2ba7be186579569b8f16c1a07ec0ef498a0f Mon Sep 17 00:00:00 2001
From: David Federman <dfederm@microsoft.com>
Date: Fri, 29 Mar 2024 09:01:51 -0700
Subject: [PATCH] RunVSTest: Notify MSBuild TerminalLogger that tests are
 starting (#550)

---
 src/RunTests/build/Microsoft.Build.RunVSTest.targets | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/src/RunTests/build/Microsoft.Build.RunVSTest.targets b/src/RunTests/build/Microsoft.Build.RunVSTest.targets
index 9529e7f..e19751a 100644
--- a/src/RunTests/build/Microsoft.Build.RunVSTest.targets
+++ b/src/RunTests/build/Microsoft.Build.RunVSTest.targets
@@ -9,6 +9,13 @@
 
   <!-- Only consider non "dotnet" scenarios sinces those are already covered by Microsoft.Testing.Platform.MSBuild, which is automatically included as a dependency of MSTest.TestAdapter -->
   <Target Name="RunVSTest" AfterTargets="Test" Condition="'$(RunVSTest)' != 'false' and '$(IsTestProject)' == 'true' and '$(MSBuildRuntimeType)' != 'Core'">
+    <!--
+      This target name is hardcoded in TerminalLogger to mean start of test workload.
+      This let's terminal logger know that it should show `Testing` in the output,
+      and not the additional internal details, such as target names.
+    -->
+    <CallTarget Targets="_TestRunStart" />
+
     <RunVSTestTask ToolExe="$(VSTestToolExe)"
                    ToolPath="$(VSTestToolPath)"
                    TestFileFullPath="$(TargetPath)"
@@ -35,4 +42,6 @@
                    VSTestArtifactsProcessingMode="$(VSTestArtifactsProcessingMode)"
                    VSTestSessionCorrelationId="$(VSTestSessionCorrelationId)" />
   </Target>
+
+  <Target Name="_TestRunStart" />
 </Project>