Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support redirecting terminal output during tests to a logfile #36

Open
jimporter opened this issue Mar 7, 2018 · 2 comments
Open

Support redirecting terminal output during tests to a logfile #36

jimporter opened this issue Mar 7, 2018 · 2 comments
Assignees
Milestone

Comments

@jimporter
Copy link
Owner

(Spun out from #33)

Instead of having to choose between suppressing terminal output and showing it in-line with your test results, there should be a way to pipe it to a file (or possibly multiple files; maybe one per test run?). This might look something like the following:

  • --print-terminal: Renamed from --show-terminal, used for printing to the console
  • --pipe-terminal: Pipe to a file; by default, this would be something like mettle-{date}.log, but users could specify a different filename (possibly as a format string to fill in the current date?)
@luav
Copy link
Contributor

luav commented Mar 7, 2018

It is important to be able to redirect stdout and stderr to the dedicated files.
So, either something like --pipe-stdout and --pipe-stderr should be provided,
or the --pipe-terminal should support both specification of the redirecting output stream(s) and the output file having 2 parameters. The latter might be confusing because it requires to apply double option to redirect streams to distinct files: --pipe-terminal stdout <stdout_file> --pipe-terminal stderr <stderr_file>.

@jimporter
Copy link
Owner Author

jimporter commented Mar 8, 2018

--pipe-stdout/--pipe-stderr probably makes the most sense then (though I guess it's not really a pipe, so I'll have to make a better name).

@jimporter jimporter added this to the 1.0 milestone Oct 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants