[pytest-dev] Customising repr() output for super-expressions of failed assertions
Craig de Stigter
craig.ds at gmail.com
Thu Jun 13 05:19:43 EDT 2019
Thanks for the replies.
We do already use the print-before-assert pattern. It'd be nice to be able
to fold this away in a hook so each individual request test doesn't need to
think about it. But using print() is perfectly fine too :)
On Thu, 13 Jun 2019 at 19:35, Joep Schuurkes <j19sch at gmail.com> wrote:
> On Thu, Jun 13, 2019, 10:25 Florian Bruhin <me at the-compiler.org> wrote:
>> On Thu, Jun 13, 2019 at 12:02:01PM +1200, Craig de Stigter wrote:
>> > This output isn't terribly useful at present. We'd like to automatically
>> > dump the request body (`r.content`) in the output, wherever it's a
>> > response object, to aid debugging.
>> It'd be cool if this were possible with hooks (I'm not sure whether it
>> is) -
>> but FWIW, what I've done so far in such situations is "print(r.content)"
>> in the
>> test. That way, pytest shows you the output when a test failed, but hides
>> for passing tests.
>> https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP)
>> GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
>> I love long mails! | https://email.is-not-s.ms/
>> pytest-dev mailing list
>> pytest-dev at python.org
> We use logging similar to the print mentioned by Florian. I also created a
> pytest plugin to have some options for how the generated logs are written
> to file: https://pypi.org/project/pytest-logfest/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pytest-dev