[TIP] Best practice for failing tests

Florian Bruhin me at the-compiler.org
Thu Mar 22 11:00:57 PDT 2018

On Thu, Mar 22, 2018 at 01:26:41PM +0000, Bruno Oliveira wrote:
> `strict=True` means that, if the fake is fixed (either by you or someone
> else), then the test suite will *fail*, which will alert you of the fact
> and then you can remove the `xfail` marker. :)

I'd recommend setting "xfail_strict = true" in pytest.ini instead, which
means *all* xfail markers will be strict by default. IMHO, they really
should be strict by default (but aren't for historical reasons).


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/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20180322/7b6d9285/attachment.pgp>

More information about the testing-in-python mailing list