-
Notifications
You must be signed in to change notification settings - Fork 638
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
Captured log to outfile #979
Comments
The
OTHERWISE: Logging is for diagnostics. SEE ALSO: |
Thanks for your explanations @jenisys . I think that is exactly as far as I got. So how would I go about putting formatter-output and logging output to the same file? I need the full output of I tried: using the same file for Do I need to write a formatter which makes use of the captured logs at each step? How would I do that? |
Why would you want to do that?
If you really want to that:
# -- ASSUMPTION: Logging handler(s) write output to stdout
$ behave -f plain features > combined_output.txt |
Why would I want to do what exactly? For me it's a pretty obvious use case: I want a logfile which has behave's explanation of what steps are executed, and in between the log output of the thing under test. Just as I have when I use I guess I could use the |
Mmh, how is step execution then tracked and output for it generated by a DETAILS:
|
There doesn't seem to be a way to get the captured logs into a log file, using the
--outfile
option.I can get it to the console using
--no-logcapture
and--format=plain
, but not to the output file using any formatter.How would I go ahead if I wanted:
--format=pretty
in the console (no log output on success)--format=plain
with--logging-level=DEBUG
to an--outfile
output file (on success and failure, no difference)?
Related to: #412
The text was updated successfully, but these errors were encountered: