<p dir="ltr">Thanks for the responses so far.</p>
<p dir="ltr">I had seen the snippet, but I try to stay runner-agnostic when possible.</p>
<p dir="ltr">I'll play around with it a bit more to see if I can mold it into something I can still use when not running via pytest.</p>
<div class="gmail_quote">On Feb 10, 2013 5:46 PM, "Robert Collins" <<a href="mailto:robertc@robertcollins.net">robertc@robertcollins.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 11 February 2013 11:42, holger krekel <<a href="mailto:holger@merlinux.eu">holger@merlinux.eu</a>> wrote:<br>
> Hi Julian,<br>
<br>
> however, i guess you are aware of this testscenario/pytest porting snippet:<br>
><br>
> <a href="http://pytest.org/latest/example/parametrize.html#a-quick-port-of-testscenarios" target="_blank">http://pytest.org/latest/example/parametrize.html#a-quick-port-of-testscenarios</a><br>
><br>
> It allows to use pytest with scenario definitions. It's passing the<br>
> argument in rather than setting an instance attribute. If you use this<br>
> method, it's also fully compatible with all other pytest options and<br>
> parametrization methods and scopes (see on that page for more examples),<br>
> and of course generally compatible to the fixture dependency injection<br>
> mechanism (<a href="http://pytest.org/latest/fixture.html" target="_blank">http://pytest.org/latest/fixture.html</a>)<br>
<br>
Hi Holger, I wasn't aware of that.<br>
<br>
Julian, testscenarios.generate_scenarios may help - you can do the<br>
parameterisation at collection time which sounds like it would work<br>
better for py.test.<br>
<br>
-Rob<br>
<br>
--<br>
Robert Collins <<a href="mailto:rbtcollins@hp.com">rbtcollins@hp.com</a>><br>
Distinguished Technologist<br>
HP Cloud Services<br>
</blockquote></div>