[ovirt-devel] Re: Porting basic suite to pytest

On Thu, Mar 5, 2020 at 3:18 PM Marcin Sobczyk <msobczyk(a)redhat.com&gt; wrote: > > Hi All, > > I've been experimenting with porting basic suite from nose to pytest. > The rationale behind my efforts were nose being deprecated since a long > time [1] and the ability to use pytest's awesome fixtures. > > Turns out it's not really that hard - with two patches [2][3] I was able > to lay the groundwork for non-distruptive and incremental process > of porting the basic suite module by module. You can find the steps > needed to port a certain module described in [2]. Please find > the patches that do the actual porting in this topic [4]. Awesome! > One of the hurdles of using pytest vs nose is that the former executes > the test functions in the order they appear in the module. This comes > from the reasoning, that tests should be independent, which is not the > case for OST. Reordering the test functions to match '_TEST_LIST' > for '002_bootstrap' and '004_basic_sanity' modules would make > a huge disruption, so I've decided to use a 'pytest-ordering' plugin that > allows you to define the order with &#39;(a)pytest.mark.run(order=)&#39; decorators. Until we get rid of dependencies between tests, this sounds like a reasonable solution.

_______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/MAU6DKOV3LB...