fix(ProgressReport): Replace progress reporting

[eNeRGy164]

Implement ShellProgressBar and make MutantsResultReporter obsolete

This is a WIP, to first get some feedback.
Added Unit testing.

Closes #519

[rouke-broersma]

Looks good to me 🐝

[rouke-broersma]

Mhm after testing it looks like the fancy progress bar does not work correctly in the visual studio debug console

This happens only when debug logging is turned on

In git bash it fails completely

It does work in CMD, but only with debug logging off:

Git bash and the visual studio debug console are probably not the main shells used to run stryker but it suggests to me that the used library does not support all shells so a bit more error handling could not hurt.

Especially the issue in git bash is concerning because that is the same issue we noticed on macOSX before and is why we disabled replacing values when Console.CursorTop caused an exception:

stryker-net/src/Stryker.Core/Stryker.Core/Reporters/Progress/ConsoleOneLineLogger.cs

Lines 62 to 74 in b05a5f9

	private bool EnvironmentHasConsole()
	{
	try
	{
	var t = Console.CursorTop;
	return true;
	}
	catch (System.IO.IOException)
	{
	return false;
	}
	}
	}

[eNeRGy164]

Mpdreamz/shellprogressbar#22
Some of these seem to be there for a while.

[rouke-broersma]

Does anyone know someone with a mac that could test this pr? 😅

[richardwerkman]

@vngrp has a mac, maybe he could take a look?

[eNeRGy164]

I have no environment to recreate these issues.

Works for me:

• Windows PowerShell 5.1
• PowerShell Core 7
• Windows cmd
• PowerShell terminal in VSCode
  
• Visual Studio Debug Conole
  

[eNeRGy164]

Mhm after testing it looks like the fancy progress bar does not work correctly in the visual studio debug console

This happens only when debug logging is turned on

Ah missed that remark.
Yes, you can't have multiple processes doing console output at the same time if one is messing with the positions, like in this case the progressbar. That is also why I had to merge the mutant reporting and the progressbar in one output.

[rouke-broersma]

Mhm after testing it looks like the fancy progress bar does not work correctly in the visual studio debug console
This happens only when debug logging is turned on

Ah missed that remark.
Yes, you can't have multiple processes doing console output at the same time if one is messing with the positions, like in this case the progressbar. That is also why I had to merge the mutant reporting and the progressbar in one output.

Unfortunately that seems like a regression compared to the current implementation (on some terminals).
We're going to do more testing to decide what to do with this pr, as it stands it looks like we're gonna have to decide between regressions on the one hand or other issues on the other hand.

Sorry for the wait.

[eNeRGy164]

No problem, it's your project after all.
I just can't reproduce the errors, so it's hard to fix them myself.

[eNeRGy164]

For showing addition logging we could reroute to the WriteLine function mentioned here: Mpdreamz/shellprogressbar#31 (comment)

[rouke-broersma]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).