in 2010 yield tests where likely still working correctly they where fundamentally broken ever since pytest introduced the collection phase -- Ronny 2018-04-11 12:46 GMT+02:00 Chris Dent <cdent@anticdent.org>:
On Sun, 8 Apr 2018, RonnyPfannschmidt wrote:
* removal of yield tests, ever since collection and test running are no
longer connected, their setupstate has been fundamentally broken for anything but test so simple, one should use parametrize
Not saying it's wrong to see them go, but back in perhaps 2010 (not really sure of the exact time) pytest's yield tests are what made me fall in love with pytest.
That was back when pytest was still a thing that did some collecting of stuff named 'test_*' that has 'assert' calls in it, and not much else.
I loved that. All the fixtures, decorators, etc that we have now are nicely powerful and useful, but back when you couldn't do much in tests it meant that during TDD you couldn't do much in code either, and that was a great thing.
/me raises a glass to yield tests, bon voyage
-- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent _______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
-- Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander