Mailman 3 April 2014 - pytest-dev

pytest logo / comments welcome
by holger krekel May 15, 2014

May 15, 2014

Hi all, am thinking of providing pytest with a logo finally ... gets about time after all those years i guess :) My plan is to go for 99designs and guarantee some 250 euros for the final logo. There are a few questions they want as background where i'd like to hear opinions :) - should it be a little animal? should it be abstract? - should it contain the text "pytest" or "py.test" or nothing? - should it have snakes? - should it have a goat in some way in it? - any colors you'd prefer? - any testing tool related logos you like? happy about any comments/feedback as i feel a bit overwhelmed :) best, holger

5 6

Using print statements in pytest's teardown_method()
by Alexander Petrovich April 30, 2014

April 30, 2014

Is there any way to get them actually printed? I use pytest to run my selenium tests and I got some test failure information printed in teardown, such as fail url, fail screenshot, user, etc. But I can't find any way to get them printed. Could you suggest something, please? -- With best regards, Petrovich Alexander QA Automation Engineer Smartweb Consulting

2 1

Re: [pytest-dev] pytest logo / comments welcome
by Laura Creighton April 29, 2014

April 29, 2014

* should look good on a hoodie/t-shirt

1 0

2.6 / please help with remaining bugs
by holger krekel April 28, 2014

April 28, 2014

Hi all, i'd like to go for a 2.6 release in May. There are 16 reported bugs in pytest core remaining, however: https://bitbucket.org/hpk42/pytest/issues?component=&kind=bug&status=open&s… Could some of you help and assign issues to yourself and see about fixing or discussing them? I will focus on reviewing issue comments and PRs but also try to come up with fixes myself. thanks and best, holger

3 2

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

Print statements in teardown_method(self, method)
by Alexander Petrovich April 23, 2014

April 23, 2014

Is there any way to get them actually printed? I use pytest to run my selenium tests and I got some test failure information printed in teardown, such as fail url, fail screenshot path, user, etc. But I can't find any way to get them printed. Could you suggest something, please? -- With best regards, Petrovich Alexander QA Automation Engineer Smartweb Consulting

2 1

Setting up tox
by Brianna Laugher April 17, 2014

April 17, 2014

Hello, The contributing guide ( http://pytest.org/latest/contributing.html ) is still missing a couple of steps I'm afraid... I installed tox in my virtualenv and then ran "python runtox.py -e py27,py33,flakes" as advised. At the end of the run tox tells me: ERROR: py27: could not install deps [nose, mock] ERROR: py33: InterpreterNotFound: python3.3 ERROR: flakes: could not install deps [pytest-flakes>=0.2] I can manually pip install nose, mock and pytest-flakes, but I don't know how to make python3.3 (which I have installed from my OS repo) "visible" or available to this virtualenv. Any ideas? Thanks, Brianna -- They've just been waiting in a mountain for the right moment: http://modernthings.org/

4 13

The issue with fixtures finalization
by Anton P April 15, 2014

April 15, 2014

Hi All, I found that pytest 2.5.2 doesn't finalize all fixtures. E.g. we have function and class level fixtures. In case func level fixture raises an exception, class level fixture finalization won't be called. SetupState._callfinalizers takes care only about finalizing of all fixtures with the same level. I didn't find any way to workaround this without modifying pytest code. Here is my fix: 1. add self.finalizer_exception=None attribute. 2. Modify _callfinalizers def _callfinalizers(self, colitem): finalizers = self._finalizers.pop(colitem, None) while finalizers: fin = finalizers.pop() try: fin() except (Exception, KeyboardInterrupt): # XXX Only first exception will be seen by user, # ideally all should be reported. if self.finalizer_exception is None: self.finalizer_exception = sys.exc_info() if self.finalizer_exception and not self._finalizers: py.builtin._reraise(*self.finalizer_exception) What do you think about this? Have I missed something? I assume that there could be another way to resolve the issue. Thank you in advance! Anton

1 0

Access fixtures from unittest.TestCase
by Wolfgang Schnerring April 8, 2014

April 8, 2014

Hello, is there a way to access a fixture object from inside a unitest.TestCase test function? As far as I understand, the way to combine fixtures and TestCase is like this: import pytest, unittest @pytest.mark.usefixtures('tmpdir') class MyTest(unittest.TestCase): def test_something(self): # XXX how can I get to ``tmpdir`` here? But there seems to be no way to get to the fixture object, which is rather constraining. Or am I missing something? Thanks for your help, Wolfgang

2 5

Announcement: new maintainer for pytest-cov and cov-core
by Marc Schlaich April 8, 2014

April 8, 2014

Hey, as the original author of these packages is unresponsive for almost two years now, I requested maintainer status on PyPI ( http://sourceforge.net/p/pypi/support-requests/352/). If anyone is interested in (co-)maintaining any of these packages please get in touch. I'm happy to share or transfer responsibility if someone is more suitable than me. I'm considering moving the repositories to GitHub. What do you think about that? Additionally, I got maintainer status of nose-cov and nose2-cov (because they are from the same author) but I'm not interested in actively maintaining them. If someone is willing to take these over just let me know. Regards, Marc

2 1