<p dir="ltr"> I would like to know if I need to look into this deprecation further: We use yield in fixtures but that's different from "yield tests" right?</p>
<br><div class="gmail_quote"><div dir="ltr">On Wed, Dec 7, 2016, 3:56 PM Ronny Pfannschmidt <<a href="mailto:opensource@ronnypfannschmidt.de">opensource@ronnypfannschmidt.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Randy,<br class="gmail_msg">
<br class="gmail_msg">
the Problem with yield tests is, that they execute test code and setup<br class="gmail_msg">
state at collection time, wich is a massive source of errors in any<br class="gmail_msg">
complex case and just barely works in the simple case<br class="gmail_msg">
<br class="gmail_msg">
back when py.test collected and executed tests as it discovered them,<br class="gmail_msg">
that was fine, but its been quite a while now since py.test switched to<br class="gmail_msg">
collect first, then execute (around the 2.0 release i think)<br class="gmail_msg">
<br class="gmail_msg">
-- Ronny<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
Am Wed, 7 Dec 2016 15:32:12 -0500<br class="gmail_msg">
schrieb Randy Syring <<a href="mailto:randy@thesyrings.us" class="gmail_msg" target="_blank">randy@thesyrings.us</a>>:<br class="gmail_msg">
<br class="gmail_msg">
> I recently received a bunch of warnings that py.test is deprecating<br class="gmail_msg">
> yield tests. I found this PR:<br class="gmail_msg">
><br class="gmail_msg">
> <a href="https://github.com/pytest-dev/pytest/pull/1714" rel="noreferrer" class="gmail_msg" target="_blank">https://github.com/pytest-dev/pytest/pull/1714</a><br class="gmail_msg">
><br class="gmail_msg">
> But there is no real commentary there about why they are being<br class="gmail_msg">
> removed (other than they are "problematic") and what should be done<br class="gmail_msg">
> to replace them. I'm not really sure if this is problem for us or<br class="gmail_msg">
> not, I'm currently going to just call the methods myself instead of<br class="gmail_msg">
> yielding them. But wondered if there was anyone else who has further<br class="gmail_msg">
> insight into this decision who can comment.<br class="gmail_msg">
><br class="gmail_msg">
> Thanks.<br class="gmail_msg">
><br class="gmail_msg">
> *Randy Syring*<br class="gmail_msg">
> Husband | Father | Redeemed Sinner<br class="gmail_msg">
><br class="gmail_msg">
> /"For what does it profit a man to gain the whole world<br class="gmail_msg">
> and forfeit his soul?" (Mark 8:36 ESV)/<br class="gmail_msg">
><br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
testing-in-python mailing list<br class="gmail_msg">
<a href="mailto:testing-in-python@lists.idyll.org" class="gmail_msg" target="_blank">testing-in-python@lists.idyll.org</a><br class="gmail_msg">
<a href="http://lists.idyll.org/listinfo/testing-in-python" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a><br class="gmail_msg">
</blockquote></div><div dir="ltr">-- <br></div><div data-smartmail="gmail_signature"><div dir="ltr">Oliver<div>My StackOverflow contributions<br><div>My CodeProject articles</div></div><div>My Github projects</div><div>My SourceForget.net projects</div></div></div>