I think there may have been some miscommunication about the skipping of 
tests

On 07/09/15 18:20, anatoly techtonik wrote:
> So, you need a declarative way of skipping tests depending on the
> conditions, such as platform, availability of DB backend, Python
> version etc. and also need to record a reason for users WHY a test
> was skipped.

What you have described is essentially available in unittest from python2.7+

https://docs.python.org/2/library/unittest.html#skipping-tests-and-expected-failures

The issue I meant to point out is that we will still be supporting 
roundup on python2.6 which doesn't have support for this sort of test 
skipping in unittest[1]. The pytest tool can provide this sort of test 
skipping support for python2.6 (ignoring the bug mentioned earlier in 
this issue[2])

   http://pytest.org/latest/skipping.html

Using the pytest.skip() or pytest.mark.skipif() decorators would mean 
that the tests suite would be dependant on pytest - though in a fairly 
superficial way.

> And as for the subject of this ticket, I think we can try to move
> py.test. Just don't forget to include argumentation for those who
> will jump in later.

I'm not sure I understand the term "argumentation". Do you mean just 
adding a note in the CHANGES.txt file? some more detailed document? or 
something else?

SeeYa,
John.

[1] technically unittest2 could provide the skipping functionality 
back-ported to python2.6, but that would be a external dependency.

[2] I believe I have a workaround that should work until the issue is 
resolved upstream.