On Wed, Jul 23, 2008 at 12:41 PM, holger krekel <[EMAIL PROTECTED]> wrote: > Hi Ralf, >> The ability to mark test cases as "expected failures" would be nice. > > Yes, i also want something where i can checkin tests > that are marked as bugs and have some clever reporting > anhd command line options for this (at best even > be able to have a link to an issue tracker). > > maybe: > > @py.test.mark(bug=number or string, url=URL) > def test_something(): > ...
I've written a quick hack (which doesn't integrate nicely with py.test). It can be viewed here: http://code.pediapress.com/hg/mwlib/file/b75d189a01a2/mwlib/xfail.py It checks the functions docstring for a link to the issue tracker. I'm not quite sure if you want to have that decorator take an issue number/link. When you've fixed that bug, you'll remove the decorator and loose that valuable information. > > although i would like this to also work in setup_* > functions and in python 2.3 nicely, i think. > I imagine such a decorator to just set attributes > on the function, not provide a new function. > and the py.test machinery to recognize these > attributes. Makes sense? sounds good. > > Not sure i'd like to consider this for 0.9.2 to be honest > which i rather want to be a bugfix release - at least ok. > not to introduce new concepts. But i am also heavily > working on a cleanup / refactoring branch which i > consider the base for a 1.0 hopefully not too far > in the future. nice. Is there a list of active branches? the last time I looked at the svn repo, trunk looked very quiet (or I used a bad path). Thinking about it I have maybe another issue for 0.9.2. When using easy_install the greenlets module is not installed correctly. I haven't looked into this (python setup.py install works). But I will probably have a look at it in the next days.... Regards - Ralf _______________________________________________ py-dev mailing list py-dev@codespeak.net http://codespeak.net/mailman/listinfo/py-dev
