On Thu, 20 Oct 2016, Floris Bruynooghe wrote:
On 29 August 2016 at 09:31, Ronny Pfannschmidt <[email protected]> wrote:
Hi Chris,
currently there is no easy/good Replacement for the use-case you outline.
the "correct" way would be a custom py.test specific collector
Yeah, a custom collector is the way to go here. I agree that it was
never really the correct way to do this.
http://docs.pytest.org/en/latest/example/nonpython.html describes how
you want to go about this I think.
Thanks for the input. I think (if I can find the time) I can figure
out what to do. Part of the complexity is that I already have the
process which dynamically creates a bunch of subclasses of
unittest.TestCase and want to "just use them" in pytest. The yield
tests made that possible. I assume I can probably wrap those
existing testcases as Items?
Several years ago, when I started using pytest, the yield tests were
my favorite thing about it. Super simple: push out functions that
have assertions in them. That's what pytest was all about then, and
it was _glorious_. In the intervening years things have become more
complex. That's the nature of things.
--
Chris Dent ┬─┬ノ( º _ ºノ) https://anticdent.org/
freenode: cdent tw: @anticdent
_______________________________________________
pytest-dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pytest-dev
