On Tue, Jun 23, 2009 at 3:12 PM, holger krekel<hol...@merlinux.eu> wrote: >> Anyway, this only gives me py.test.xfail and not mark. > > 1. mark is not there, indeed. We could do a plugin > that provides py.test.mark - as it was undocumented > and not much advertised yet so i didn't think there > would be users :)
I didn't actually use it. so feel free to drop it. > > 2. py.test.xfail does not take arguments anymore - > see http://tinyurl.com/nxqta2 > I basically stripped the py.test.xfail decorator to the bare > minimum of marking a function as expected-to-fail. > do you have a need for it to take a message argument? no. > >> BTW, py.test.xfail doesn't work for me too; > > Hum, this happens in an interactive session because plugins > are not activated and there is no py.test.xfail entry. > If you issue > >>>> py.test.config.parse([]) >>>> py.test.config.pluginmanager.do_configure(py.test.config) > > the default plugins will be activated and py.test.xfail > becomes visible. Would you like this incantation to live in > a "py.test.init()" helper?! > no, the interactive session was just a quick test... regards, - ralf _______________________________________________ py-dev mailing list py-dev@codespeak.net http://codespeak.net/mailman/listinfo/py-dev
