Visual Studio 2013 Update 4 - VSTest.console Output SDOUT Messages DURING Test Run, NOT After Test Run Completes

Question

I am using vstest.console.exe and running a test from our internal CI build system, our internal CI build system requires console standard out to be updated at least every 30 minutes to
ensure that the process has not hung. 
I am executing the following command using a customer logger and test settings files:
vstest.console.exe /testcasefilter:"TestCategory=LongTest" /settings:"C:\testing\CodedUI.testsettings" /logger:TRX /logger:CodedUITestLogger "C:\AppTests\CodedUITest.dll" /InIsolation
I have copied and modified the following custom logger(see
here for more info):
https://github.com/ppiotrowicz/AwesomeLogger
Such that after the test is executed the pass/fail/success information is printed to the standard out console.
Tests run: 1, Errors: 0, Failures: 0, Inconclusive: 0, Time: 00:00:87.9331298 minutes
Not run: 0, Invalid: 0, Ignored: 0, Skipped: 0
It's important to be clear that the test run takes 90 minutes, it's a long running test.
Time: 00:00:87.9331298 minutes
When the test run is executed for 90 minutes I see the following and our CI build system kills the process after 30 minutes of no output, so in the failure log I see:
vstest.console.exe /testcasefilter:"TestCategory=LongTest" /settings:"C:\testing\CodedUI.testsettings" /logger:TRX /logger:CodedUITestLogger C:\AppTests\CodedUITest.dll
Microsoft (R) Test Execution Command Line Tool Version 12.0.31101.0
Copyright (c) Microsoft Corporation. All rights reserved.
Running tests in C:\testing\bin\debug\TestResults
Starting test execution, please wait...
However I have a data-driven codedUI test pulling from a csv data source, that successfully executes, however the test takes 90 minutes to run....which means that for 90 minutes the console output displayed is only:
Running tests in C:\testing\bin\debug\TestResults
Starting test execution, please wait...
How can I have vstest.console output to standard out DURING the test run to the console?
Is there a way in the .testsettings file to enable more verbose logging
DURING the test execution?
In MSTest it was possible to use the parameter (/detail:stdout) which would display info while the test was running.  
MSTEST /testcontainer:MyDllToTest.dll /testSettings.local.TestSettings /detail:stdout
Ian Ceicys

Answer 1

I ended up solving the issue for our internal CI system with the following threaded coded. I don't like that it just prints: CodedUI Test Run in progress. How can I query for a percent complete for test execution status or get a reading on the iteration
that's running for each row in the csv data source?
[Test, Category("RunCodedUITest")]
public void RunVsTestConsole()
//ARRANGE
var outputPath = "C:\Tests\bin\debug"
var codedUIAssembly = Path.Combine(outputPath, "CodedUITest.dll");
string output;
string codedUIAssemblyFile = @codedUIAssembly.ToString();
if (File.Exists(codedUIAssemblyFile))
//ACT
CodedUITestRunner codedUiTestRunnerObject = new CodedUITestRunner();
Thread workerThread = new Thread(codedUiTestRunnerObject.RunTest);
workerThread.Start();
while (workerThread.IsAlive)
TimeSpan oneminute = new TimeSpan(0, 1, 0);
Console.WriteLine("CodedUI Test Run in progress...");
Thread.Sleep(oneminute);
workerThread.Join();
Console.WriteLine("CodedUI Test Run completed.");
else
Console.WriteLine("ERROR: CodedUI Test Assembly file Does NOT exist @ Path : " + codedUIAssemblyFile);
Assert.IsTrue(File.Exists(codedUIAssemblyFile), "CodedUI Binary DLL exists!" + codedUIAssemblyFile);
public class CodedUITestRunner
// This method will be called when the thread is started.
public void RunTest()
var outputPath = "C:\Tests\bin\debug"
var codedUIAssembly = Path.Combine(outputPath, "CodedUITest.dll");
string output;
string codedUIAssemblyFile = @codedUIAssembly.ToString();
output = TestFrameworkHelper.Exec("vstest.console.exe", string.Format("/testcasefilter:\"TestCategory=LongTest\" /settings:\"C:\\tests\\CodedUI.testsettings\" /logger:TRX /logger:CodedUITestLogger {0}",
codedUIAssembly), WorkingDir: outputPath, RequestEC: false);
StringAssert.Contains("EXIT CODE: 0", output, "Exit code was not 0.");
Ian Ceicys