Closed pkrukp closed 2 months ago
Thanks for reporting this
I'm not sure if this is something we want to support. My expectation for a console test runner is that it runs to completion in a non-interactive way. I don't think I'll classify it as a bug
I thought it simply collects coverage from executed application...
I'm not sure if this is something we want to support. My expectation for a console test runner is that it runs to completion in a non-interactive way. I don't think I'll classify it as a bug
Since next version we allow e2e test coverage, so maybe also a console app that accepts input could be a use case, what do you think @tonerdo?
Do you know when that next version will be available?
Since next version we allow e2e test coverage, so maybe also a console app that accepts input could be a use case
I prefer to spend more time optimizing for the common case which is usually non-interactive runs in CI servers. Even when using the integration test feature
Moved to enhancement
@pkruk2 the idea is to release within end of the year.
This issue is stale because it has been open for 3 months with no activity.
This issue was closed because it has been inactive for 9 months since being marked as stale.
Hello,
I tried to collect application coverage (
coverlet.exe
) from a simple .net core 3.1 console application which reads from standard input (Console.ReadKey()
). I got an exception. It looks like coverlet.exe does not provide/pass/redirect standard input to the executed program.The error I got was:
Attaching the console2 project for your convenience: console2.zip
I'm using coverlet.exe 1.7.0.0