Mailman 3 January 2014 - pytest-dev

py.test and decorators
by Sarah Mount April 25, 2014

April 25, 2014

Hi there, I am currently converting some very idiosyncratic hand-rolled tests into more sensible unit tests with pytest. I had a problem running tests which dealt with decorators and following the advice here: http://stackoverflow.com/questions/19614658/how-do-i-make-pytest-fixtures-w… I refactored all my decorators to use the decorator library rather than functools.wraps. The win there was that now the Python 2.7 version of my code behaves in the same way as the Python 3.3 code (whereas before the 2.7 code passed and the 3.3 code errored). The fail is that now none of the tests run at all! I tried running tests without py.test (as in: python -m mylib.test.test_one) and they ran as expected. If I try to use the library just from a REPL session it seems OK. I suspect that the issue has occurred because I haven't yet understood where to use pytest fixtures. The (simplified) code looks roughly like this: ### FILE base.py @process def foo(channel): channel.write(100) @process def bar(channel): channel.read() ### FILE test_one.py def test_one_one(): channel = Channel() par(foo(channel), bar(channel)).start() And the results look like this: $ py.test mylib/ ================================================================ test session starts ================================================================= platform linux2 -- Python 2.7.5 -- pytest-2.5.1 collected 44 items mylib/test/test_one.py (venv)$ I have tried putting the @pytest.fixture decorator on both the functions in base.py and those in test_one.py but neither works. Any ideas? Thanks, Sarah -- Sarah Mount, Senior Lecturer, University of Wolverhampton website: http://www.snim2.org/ twitter: @snim2

3 7

pytest-xdist-1.10 released (distributed testing plugin)
by holger krekel Jan. 29, 2014

Jan. 29, 2014

Hi all, also released pytest-xdist-1.11 with some little improvements and speedups regarding overheads for distributing tests (maybe 10%, not too much). Install it with: pip install -U pytest-xdist and checkout the pypi page: https://pypi.python.org/pypi/pytest-xdist best, holger 1.10 ------------------------- - add glob support for rsyncignores, add command line option to pass additional rsyncignores. Thanks Anatoly Bubenkov. - fix pytest issue382 - produce "pytest_runtest_logstart" event again in master. Thanks Aron Curzon. - fix pytest issue419 by sending/receiving indices into the test collection instead of node ids (which are not neccessarily unique for functions parametrized with duplicate values) - send multiple "to test" indices in one network message to a slave and improve heuristics for sending chunks where the chunksize depends on the number of remaining tests rather than fixed numbers. This reduces the number of master -> node messages (but not the reverse direction)

1 0

pytest-2.5.2: fixes, plugin index, contribution guide
by holger krekel Jan. 29, 2014

Jan. 29, 2014

pytest-2.5.2: fixes, plugin page, contribution guide =========================================================================== pytest is a mature Python testing tool with more than a 1000 tests against itself, passing on many different interpreters and platforms. The 2.5.2 release fixes a few bugs with two maybe-bugs remaining and actively being worked on (and waiting for the bug reporter's input). We also have a new contribution guide thanks to Piotr Banaszkiewicz and an improved 3rd party plugin overview (including py2/py3 tests) page thanks to Bruno Oliveira. See docs at: http://pytest.org As usual, you can upgrade from pypi via:: pip install -U pytest Thanks to the following people who contributed to this release: Anatoly Bubenkov Ronny Pfannschmidt Floris Bruynooghe Bruno Oliveira Andreas Pelme Jurko Gospodnetić Piotr Banaszkiewicz Simon Liedtke lakka Lukasz Balcerzak Philippe Muller Daniel Hahler have fun, holger krekel 2.5.2 ----------------------------------- - fix issue409 -- better interoperate with cx_freeze by not trying to import from collections.abc which causes problems for py27/cx_freeze. Thanks Wolfgang L. for reporting and tracking it down. - fixed docs and code to use "pytest" instead of "py.test" almost everywhere. Thanks Jurko Gospodnetic for the complete PR. - fix issue425: mention at end of "py.test -h" that --markers and --fixtures work according to specified test path (or current dir) - fix issue413: exceptions with unicode attributes are now printed correctly also on python2 and with pytest-xdist runs. (the fix requires py-1.4.20) - copy, cleanup and integrate py.io capture from pylib 1.4.20.dev2 (rev 13d9af95547e) - address issue416: clarify docs as to conftest.py loading semantics - fix issue429: comparing byte strings with non-ascii chars in assert expressions now work better. Thanks Floris Bruynooghe. - make capfd/capsys.capture private, its unused and shouldnt be exposed

1 0

pytest bug day TODAY / etherpad
by holger krekel Jan. 22, 2014

Jan. 22, 2014

Hi folks, here is the etherpad for today's BUG day: http://etherpad.osuosl.org/as4wyG3FLn i'll need to bring my son to child care and will then join around 10AM UTC+1. cheers, holger

1 0

Changing the behavior of --junitxml
by achartier＠fastmail.fm Jan. 22, 2014

Jan. 22, 2014

Hi, I would like to propose a change to the behavior of the --junitxml option. Currently, if the same XML file path is specified for multiple invocations of pytest, the file is overwritten. For our use case, we would like the ability to append new test results to an existing JUnit XML file so we don't lose previous results. This is important for us, as we are automating calls to pytest and would like to avoid the need to create a consolidated JUnit XML results file ourselves (i.e., by specifying a different argument to --junitxml for each invocation and then consolidating all the separate XML files into a single one for consumption by our tool). Is this behavior change something that could be considered for the next release of pytest? If other pytest users are relying on the existing overwriting behavior of --junitxml, perhaps another pytest option could be added to toggle between overwrite and append behavior. Best, Alfonso

3 3

reminder: pytest bug day tomorrow (wednesday)
by holger krekel Jan. 21, 2014

Jan. 21, 2014

Hi all, bug day is tomorrow starting around 9-10AM UTC+1 on #pylib irc.freenode.net. see you, holger ----- Forwarded message from holger krekel <holger(a)merlinux.eu> ----- Date: Tue, 14 Jan 2014 18:18:00 +0000 From: holger krekel <holger(a)merlinux.eu> To: pytest-dev(a)python.org Subject: [pytest-dev] next bug day: wednesday 22nd jan 2014 User-Agent: Mutt/1.5.20 (2009-06-14) the doodle has closed and we are going to do the next bug/issue day 22nd Jan 2014 (wednesday). The following people plan to attend: Andreas Pelme Anatoly Bubenkov Floris Bruynooghe Holger Krekel Ronny Pfannschmidt If you can't come please try drop a note the day before. If you didn't register with the doodle but want to come, please feel free to show up on IRC. cheers, holger _______________________________________________ Pytest-dev mailing list Pytest-dev(a)python.org https://mail.python.org/mailman/listinfo/pytest-dev ----- End forwarded message -----

1 0

unitest -> pytest differences / welcome from unittest
by holger krekel Jan. 20, 2014

Jan. 20, 2014

Hi all, if someone is rather freshly into pytest and previously used unittest: could you write about what you experienced as main differences, especially stumbling blocks? longer-time pytest users who well remember things may also contribute of course :) I'd then like to make this into a little "welcome from unittest" page on pytest.org. best & thanks, holger

1 0

next bug day: wednesday 22nd jan 2014
by holger krekel Jan. 14, 2014

Jan. 14, 2014

the doodle has closed and we are going to do the next bug/issue day 22nd Jan 2014 (wednesday). The following people plan to attend: Andreas Pelme Anatoly Bubenkov Floris Bruynooghe Holger Krekel Ronny Pfannschmidt If you can't come please try drop a note the day before. If you didn't register with the doodle but want to come, please feel free to show up on IRC. cheers, holger

2 2

HowTo re-run test function N times?
by Anton P Jan. 14, 2014

Jan. 14, 2014

Hi All, We need to create plugin that allows us to re-run some test case N times (or until failure). We found 2 possible solutions: 1) Using copy module we copy items on pytest_collection_modifyitems hook. This works good (-x option allows to re-run until the first failure) But this works very slow in case there are a lot of items in collection because filtering isn't performed yet. 2) Also there is alredy developed plugin ( https://github.com/klrmn/pytest-rerunfailures/blob/master/rerunfailures/plu…). But it doesn't work with test classes. Does anybody have any ideas about fast and universal solution? Thank you in advance! Anton

2 1

Autocompletion on fixture objects as test function input arguments - PyCharm
by Michelle Chartier Jan. 13, 2014

Jan. 13, 2014

Hey all, I recently got the community edition PyCharm IDE and so far like a lot of things about it (especially the ability to run pytest tests from within it). HOWEVER, I am having a problem with auto-completion on fixture functions (I realize this may not be the place to ask this question but I was hoping someone had some info that could help me or point me somewhere :) ) So, the problem: in my test function I am using a fixture object as an input argument and want to be able to see all available functions with autocompletion. To see autocompletion in Aptana, I imported the necessary fixture to the test module where my test function resides (the fixture is imported to a conftest in a package I have defined) ---------------------------------- Example: #this test module resides in mypackag.mysubpackage.mysubsubpackage from mypackage.mysubpackage.conftest import myobj def test_mytest(myobj): myobj. (<- this is where the autocompletion should show up?) ---------------------------------- In Aptana myobj shows all the available functions with autocompletion as expected but in PyCharm (with the exact same code/folders/folder structure) it says "No suggestions." Anyone have a similar problem or know of a solution? (I would prefer to stick with PyCharm... :) ) Thanks! Michelle

3 2