How are Console being tested these days?

Question

.NET

Hello!
It's simple:
- console program
- text input / output from the console. (no color, etc.)
Need to test I/O pairs with NUnit.
At the moment everything is WORKING through

Console.SetOut and StringWriter

but would like an alternative. Including for running tests in parallel.
Sawing 100500 interfaces? The internet is full of contradictions...

Answer 1

This is exactly the problem for the solution of which they came up with Dependency Injection. If you hardwire to a static class Console, you have to put up with its limitations, in particular, single-threading.
The most competent solution, for which you will not be ashamed, is indeed to use DI and an interface. We will have to implement two classes based on it - "combat" ConsoleWrapperand test ConsoleWrapperMock.
As a quick and dirty solution - if the program is simple and you can test everything through the input parameters, you can run it as an external process in the test (call the exe file) - then the processes will be independent of each other and the tests can be run in parallel.