<div dir="ltr">Hi Dan,<div><br></div><div>(Cool to know you use pytest-qt :))<br><br><div class="gmail_quote"><div dir="ltr">On Thu, Jan 4, 2018 at 7:31 PM Dan Nealschneider &lt;<a href="mailto:dan.nealschneider@schrodinger.com">dan.nealschneider@schrodinger.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>1. How should I ensure that start_qapp is run before any test or test setup?<br></div></div></blockquote><div><br></div><div>Unfortunately the only way I know of is to change your setUpClass method into an autouse fixture, this technique is detailed here: <a href="https://github.com/pytest-dev/pytest/issues/517#issuecomment-128150676">https://github.com/pytest-dev/pytest/issues/517#issuecomment-128150676</a> </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>2. Does this seem like a bug/RFE that I should report to pytest?</div></div></blockquote><div><br></div><div>This has actually been discussed extensively [1] and there is an implementation idea which is easy to implement and would make xunit setup/fixtures work better together [2] but there&#39;s the concern of breaking backward compatibility: definitely there are people who depend on the current behavior and just changing this would break their test suite in subtle and no fun ways [3].</div><div><br></div><div>[1] <a href="https://github.com/pytest-dev/pytest/issues/517">https://github.com/pytest-dev/pytest/issues/517</a> </div><div>[2] <a href="https://github.com/pytest-dev/pytest/issues/517#issuecomment-228830714">https://github.com/pytest-dev/pytest/issues/517#issuecomment-228830714</a></div><div>[3] <a href="https://github.com/pytest-dev/pytest/issues/517#issuecomment-229506416">https://github.com/pytest-dev/pytest/issues/517#issuecomment-229506416</a></div><div><br></div><div>Cheers,</div><div>Bruno.</div></div></div></div>