Better guidance in --result-log deprecation warning #2739
Closed
Labels
Comments
@thebjorn you are absolutely right, we should include a link in the warnings message to the I think one of the suggestions was to use pytest-tap or create a new external plugin which would generate a stream of JSON objects. |
nicoddemus
added a commit
to nicoddemus/pytest
that referenced
this issue
Aug 31, 2017
fgmacedo
added a commit
to fgmacedo/pytest
that referenced
this issue
Sep 4, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current warnings summary when using
--result-log
looks like this:which doesn't give any information on what to use instead, possible work-arounds, links to more information, etc.
The link to warnings.html looks promising but is a red-herring. Perhaps a more distinctive way of indicating that it isn't related to the
--result-log
warning can be found?I wasn't actually using the output of
--result-log
for anything so the easiest solution was just to remove the usage of the switch (but I didn't think to look at the contents until after I'd found #1812 and #830..)The text was updated successfully, but these errors were encountered: