Mailman 3 July 2013 - pytest-dev

pytest bug day tomorrow
by holger krekel July 31, 2013

July 31, 2013

Hi again, just a quick reminder that tomorrow is pytest bug day, torwards the 2.4 release! See you on #pylib. cheers, holger

1 0

first pytest bug day 1st August 2013
by holger krekel July 23, 2013

July 23, 2013

Hi pytesters, First of August is going to see the first public pytest-bug-thursday. We'll co-ordinate through #pylib on irc.freenode.net, and i'll be present at german office times as well as in the evening. Hope to see many of you helping to fix bugs and prepare the pytest-2.4 release! There is something for everybody to trickle, we have a full bucket :) cheers, holger

1 0

new "professional testing with Python" training in germany
by holger krekel July 16, 2013

July 16, 2013

For those interested, i am giving another open "professional testing with Python" training at the PythonAcademy in Leipzig, end November. For details: http://www.python-academy.com/courses/specialtopics/python_course_testing.h… feel free to mail me personally if you have any questions. cheers, holger

1 0

Re: [pytest-dev] [pytest-rerunfailures] pytest-rerunfailures not using fixtures on reruns (#10)
by Leah Klearman July 16, 2013

July 16, 2013

Hi Holger and other py.test mavens, Bob has reported a problem with my py.test plugin pytest-rerunfailures [1] not re-running the setup before rerunning the test. Looking at my code, it has pytest_runtest_protocol() [2] looping on _pytest.runner.runtestprotocol() [3], which in turn runs the setup, the test, and the teardown. [1] https://github.com/klrmn/pytest-rerunfailures [2] https://github.com/klrmn/pytest-rerunfailures/blob/master/rerunfailures/plu… [3] https://bitbucket.org/hpk42/pytest/src/fdc28ac2029f1c0be1dac4991c2f1b014c39… I haven't taken the hours needed to get my head fully into py.test plugin development mode, but I'm not sure I can implement a fix at my layer. I'm hoping someone here will have some insight. Thanks, -Leah On Sun, Apr 14, 2013 at 6:29 PM, Bob Silverberg <notifications(a)github.com>wrote: > I just verified this behaviour myself with a simple test [1]. I see it > with both funcargs and fixtures, but I'm not sure if it has to do with the > plugin, or the way py.test works. It does inject the value into the test > method, but it doesn't rerun the fixture, so it seems like it is caching > the first run of the fixture and using that on subsequent runs. > > I'm not sure if this is something that the plugin can have any effect on, > or if it's just the way fixtures work. It is specified for this fixture > that it is scope='function', and perhaps py.test makes that happen by > checking the function name, which is, of course, the same for each run. I > did try removing the scope argument from the fixture but that had no > effect. > > Do you have any thoughts about this, @klrmn <https://github.com/klrmn>? > > [1] https://gist.github.com/bobsilverberg/5385035 > > — > Reply to this email directly or view it on GitHub<https://github.com/klrmn/pytest-rerunfailures/issues/10#issuecomment-163636…> > . >

4 8

github pytest mirror
by holger krekel July 10, 2013

July 10, 2013

Hi again, there now is an experimental https://github.com/hpk42/pytest mirror which you can per-use for pull requests. Issue tracking stays on bitbucket. The mirror is bidirectional but depends on me manual syncing for now. Many thanks to Anatoly Bubenkoff for helping to set this up. have forking fun, holger

1 0

next pytest bug day: August 1st
by holger krekel July 10, 2013

July 10, 2013

Hi all, mark your calendars! Due to popular request i'll start doing regular pytest bug days, for now on the first thursday of a month. The next one thus is: Thursday, August 1st, co-ordinated through #pylib on freenode i'll be there on my european work day and probably around in the evening as well. Please spread the word. cheers, holger

1 0