ooc-bdd should use deadlogger for colored output / more functionality

[nddrylliog]

You don't always want test output in stdout, and colors need to be handled differently on other OSes (Windows).

Using deadlogger instead would be nice :)

https://github.com/nddrylliog/deadlogger

[wandernauta]

deadlogger looks nice, but unless I'm absolutely sure it's got features I can't do without I'm a bit afraid of introducing a dependency (any dependency).

Where would you like to send test output for example if it isn't on stdout? Should a list of failed tests go on standard error or something like that?

Also, regarding color on Windows - how would one do that with deadlogger? Isn't this just a regular ANSI escape?

[nddrylliog]

@wandernauta Well, one dependency is not too much, but it's our lib, fair enough.

When running a large test suite, you might want to redirect the output to some Continuous Integration server instead. You could do that by running a process and getting its stdout/stderr or you could attach your own handlers to deadlogger and get that for free without relying on pipes and stuff.

For color on Windows, it's actually a property of the TTY, because cmd.exe and friends don't support ANSI escapes. See https://github.com/nddrylliog/rock/blob/master/sdk/os/native/TerminalWin32.ooc