Mailman 3 April 2013 - pytest-dev

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

devpi-server: lightning fast pypi.python.org proxy (0.7 initial release)
by holger krekel April 30, 2013

April 30, 2013

devpi-server: lightning-fast pypi.python.org proxy (0.7 initial) ================================================================= This is the initial release of devpi-server, an easy-to-use caching proxy server for pypi.python.org, providing fast and reliable installs when used by pip or easy_install. devpi-server offers features not found in other PyPI proxy servers: - transparent caching of pypi.python.org index and release files on first access, including indexes and files from 3rd party sites. - pip/easy_install/buildout are shielded from the typical client-side crawling, thus providing lightning-fast and reliable installation (on second access of a package). - ``devpi-server`` moreover automatically updates its main index cache using pypi's changelog protocol, making sure you'll always see an up-to-date view of what's available. devpi-server is designed to satisfy all needs arising from pip/easy_install installation operations and can thus act as the sole entry point for all package installation interactions. It will manage all outbound traffic for installing packages. Getting started ---------------------------- Simply install ``devpi-server`` via for example:: pip install devpi-server # or easy_install devpi-server Make sure you have the ``redis-server`` binary available and issue:: devpi-server after which a http server is running on ``localhost:3141`` and you can use the following index url with pip or easy_install:: pip install -i http://localhost:3141/ext/pypi/simple/ ... easy_install -i http://localhost:3141/ext/pypi/simple/ ... To avoid having to re-type the URL, you can configure pip by either setting the environment variable ``PIP_INDEX_URL`` to ``http://localhost:3141/ext/pypi/simple/`` or by putting an according entry in your ``$HOME/.pip/pip.conf`` (posix) or ``$HOME/pip/pip.conf`` (windows):: [global] index-url == http://localhost:3141/ext/pypi/simple/ Example timing ---------------- Here is a little screen session when using a fresh ``devpi-server`` instance, installing itself in a fresh virtualenv:: hpk@teta:~/p/devpi-server$ virtualenv devpi >/dev/null hpk@teta:~/p/devpi-server$ source devpi/bin/activate (devpi) hpk@teta:~/p/devpi-server$ time pip install -q \ -i http://localhost:3141/ext/pypi/simple/ devpi-server real 21.971s user 1.564s system 0.420s So that took 21 seconds. Now lets remove the virtualenv, recreate it and install a second time:: (devpi) hpk@teta:~/p/devpi-server$ rm -rf devpi (devpi) hpk@teta:~/p/devpi-server$ virtualenv devpi >/dev/null (devpi)hpk@teta:~/p/devpi-server$ time pip install -q -i http://localhost:3141/ext/pypi/simple/ devpi-server real 1.716s user 1.152s system 0.472s Ok, that was more than 10 times faster. The install of ``devpi-server`` (0.7) involves five packages btw: ``beautifulsoup4, bottle, py, redis, requests``. Compatibility -------------------- ``devpi-server`` works with python2.6 and python2.7 on both Linux and Windows environments. Windows support is somewhat experimental -- better don't run a company wide server with it. OSX is untested as of now but no issues are expected -- please report back how things work in reality. ``devpi-server`` requires ``redis-server`` with versions 2.4 or later. Earlier versions may or may not work (untested). Deployment notes ---------------------------- By default, devpi-server configures and starts its own redis instance. For this it needs to find a ``redis-server`` executable. On windows it will, in addition to the PATH variable, also check for ``c:\\program files\redis\redis-server.exe`` which is the default install location for the `windows redis fork installer <https://github.com/rgl/redis/downloads>`_. In a consolidated setting you might want to use the ``--redismode=manual`` and ``--redisport NUM`` options to rather control the setup of redis yourself. You might also want to use the ``--datadir`` option to specify where release files will be cached. Lastly, if you run ``devpi-server`` in a company network, you can for example proxy-serve the application through an nginx site configuration like this:: # sample nginx conf server { server_name your.server.name; listen 80; root /home/devpi/.devpi/httpfiles/; # arbitrary for now location / { proxy_pass http://localhost:3141; proxy_set_header X-Real-IP $remote_addr; } } command line options --------------------- A list of all devpi-server options:: $ devpi-server -h Usage: devpi-server [options] Options: -h, --help show this help message and exit main options: --version show devpi_version (0.7) --datadir=DIR data directory for devpi-server [~/.devpi/serverdata] --port=PORT port to listen for http requests [3141] --redisport=PORT redis server port number [3142] --redismode=auto|manual whether to start redis as a sub process [auto] --bottleserver=TYPE bottle server class, you may try eventlet or others [wsgiref] --debug run wsgi application with debug logging pypi upstream options: --pypiurl=url base url of remote pypi server [https://pypi.python.org/] --refresh=SECS periodically pull changes from pypi.python.org [60] Project status and next steps ----------------------------- ``devpi-server`` is considered beta because it's just an initial release. It is is tested through tox and has all of its automated pytest suite passing for python2.7 and python2.6 on Ubuntu 12.04 and Windows 7. ``devpi-server`` is actively developed and is bound to see more releases in 2013, in particular for supporting private indexes and a new development and testing workflow system. You are very welcome to join, discuss and contribute: * mailing list: https://groups.google.com/d/forum/devpi-dev * repository: http://bitbucket.org/hpk42/devpi-server * issues: http://bitbucket.org/hpk42/devpi-server/issues * irc: for now on #pylib on irc.freenode.net. * pypi home page: https://pypi.python.org/pypi/devpi-server

1 0

pytest-2.3.5: bug fixes and little improvements
by holger krekel April 30, 2013

April 30, 2013

pytest-2.3.5: bug fixes and little improvements =========================================================================== pytest-2.3.5 is a maintenance release with many bug fixes and little improvements. See the changelog below for details. No backward compatibility issues are foreseen and all plugins which worked with the prior version are expected to work unmodified. Speaking of which, a few interesting new plugins saw the light last month: - pytest-instafail: show failure information while tests are running - pytest-qt: testing of GUI applications written with QT/Pyside - pytest-xprocess: managing external processes across test runs - pytest-random: randomize test ordering And several others like pytest-django saw maintenance releases. For a more complete list, check out https://pypi.python.org/pypi?%3Aaction=search&term=pytest&submit=search. For general information see: http://pytest.org/ To install or upgrade pytest: pip install -U pytest # or easy_install -U pytest Particular thanks to Floris, Ronny, Benjamin and the many bug reporters and fix providers. may the fixtures be with you, holger krekel Changes between 2.3.4 and 2.3.5 ----------------------------------- - never consider a fixture function for test function collection - allow re-running of test items / helps to fix pytest-reruntests plugin and also help to keep less fixture/resource references alive - put captured stdout/stderr into junitxml output even for passing tests (thanks Adam Goucher) - Issue 265 - integrate nose setup/teardown with setupstate so it doesnt try to teardown if it did not setup - issue 271 - dont write junitxml on slave nodes - Issue 274 - dont try to show full doctest example when doctest does not know the example location - issue 280 - disable assertion rewriting on buggy CPython 2.6.0 - inject "getfixture()" helper to retrieve fixtures from doctests, thanks Andreas Zeidler - issue 259 - when assertion rewriting, be consistent with the default source encoding of ASCII on Python 2 - issue 251 - report a skip instead of ignoring classes with init - issue250 unicode/str mixes in parametrization names and values now works - issue257, assertion-triggered compilation of source ending in a comment line doesn't blow up in python2.5 (fixed through py>=1.4.13.dev6) - fix --genscript option to generate standalone scripts that also work with python3.3 (importer ordering) - issue171 - in assertion rewriting, show the repr of some global variables - fix option help for "-k" - move long description of distribution into README.rst - improve docstring for metafunc.parametrize() - fix bug where using capsys with pytest.set_trace() in a test function would break when looking at capsys.readouterr() - allow to specify prefixes starting with "_" when customizing python_functions test discovery. (thanks Graham Horler) - improve PYTEST_DEBUG tracing output by puting extra data on a new lines with additional indent - ensure OutcomeExceptions like skip/fail have initialized exception attributes - issue 260 - don't use nose special setup on plain unittest cases - fix issue134 - print the collect errors that prevent running specified test items - fix issue266 - accept unicode in MarkEvaluator expressions

1 0

parametrize + xfail
by Brianna Laugher April 23, 2013

April 23, 2013

Hi again :) A common problem I have is that I have a test that is parametrized with py.test.mark.parametrize, I discover a bug, I want to add another test case for that bug and mark it as xfail. I have done something based on http://stackoverflow.com/questions/12364801/how-to-mark-some-generated-test… for pytest_generate type functions, but it is awkward to do without disrupting the existing cases, and somewhat overkill in cases where the xfail is likely to be resolved (the bug is fixed) soon. With py.test.mark.parametrize, I notice https://bitbucket.org/hpk42/pytest/issue/124/allow-individual-parametrized-… I was just thinking about this now and I wonder if it is possible to build a decorator like this? @py.test.mark.parametrizexfail('duration', 'expectedBrackets'), [ (7, [None, None, None, 7]), (19, [None, 7, 6, 6]), ]) @py.test.mark.parametrize(('duration', 'expectedBrackets'), [ (24, [6, 6, 6, 6]), (23, [6, 6, 6, 6]), (25, [6, 6, 6, 6]), ]) So 5 cases would be fed into the test, with only the first two marked as xfail. Also while I'm at it, it could be good for pytest to issue a warning if someone uses a mark called parameterize, parametrise or parameterise, because I've been caught pondering why a mark wasn't working properly at least once :) cheers Brianna -- They've just been waiting in a mountain for the right moment: http://modernthings.org/

2 3

Using a context manager in a funcarg/fixture
by Brianna Laugher April 23, 2013

April 23, 2013

Hi folks, I posted this a couple of weeks ago and would appreciate if anyone can offer a useful answer. http://stackoverflow.com/questions/15801662/py-test-how-to-use-a-context-ma… I feel like some kind of fixture definition that involves a yield statement could be usefulfor this? cheers Brianna -- They've just been waiting in a mountain for the right moment: http://modernthings.org/

3 5

Announce: pytest-qt: fixture for testing PySide and PyQt applications
by Bruno Oliveira April 19, 2013

April 19, 2013

Hello all, I would like to announce pytest-qt, which is a pytest plugin that helps writing tests for GUIs written in PySide or PyQt. The plugin introduces a new fixture, qtbot, which contains functions to send events to one or more widgets like a real user, allowing you to test GUI specific behaviors. Current release is 1.0 which contains the basic API, but more functionality to make GUI testing easier should be added in the future. Docs: https://pytest-qt.readthedocs.org<https://pytest-qt.readthedocs.org/en/latest/> Repo: https://github.com/nicoddemus/pytest-qt Best Regards, Bruno

1 0

Questions about paramtrize and csv files
by Thomas CARPENTIER April 18, 2013

April 18, 2013

Hi, I'm working with pytest since few weeks now for automate my functionnal tests using Webdriver and python. And i have some questions about how to paramatrize tests. After reading docs, i've setup my tests like : @pytest.mark.parametrize(("Url", "name", "LastName", "IdCustomer"), [ ("http://myurl.com", "myname", "mylastname", "12345"), ]) def test_get_infos_about_client(Url, name, Lastname, IdCustomer): #Do something with arguments [...] My problem is I've 2 testing environnements ENV1 and ENV2, however datas ( in particular IdCustomer are not the same between ENV1 and ENV2 ( these datas are generated during the creation of the Customer) So , I'm thinking about use csv files to inject datas in place of parametrize function. But I did'nt find any docs about it. Is it possible? I've tried def pytest_generate_tests(metafunc): #read csv file metafunc.parametrize(header, datas) But it doesn't work! Can I do the same thing with another method ? Thnaks for your help Thomas

2 6

pytest-cov +gevent reporting incorrect results
by Ofer Nave April 17, 2013

April 17, 2013

Anyone have experience using pytest-cov on a codebase that makes use of gevent greenlets? I just started using pytest-cov for the first time yesterday, and thought it'd be fun to try to get my test coverage from 85% to 100%. However, the last few reportedly not-covered lines are, in fact, executed multiple times. I'm 100% certain of this (it's a critical section, the whole system depends on it, and I've added print statements just to be dumbly sure). The only possibility that comes to mind is that perhaps this is because those sections of code are in a spawned greenlet, and maybe that messes with how pytest-cov works -- can't be sure because I don't know how it works. :) -ofer

2 1

excluding marked tests as default behavior
by Ofer Nave April 16, 2013

April 16, 2013

I understand I can mark tests with `(a)pytest.mark.whatever` and run them specifically with `pytest -m whatever`, or run skip them with `pytest -m 'not whatever'`. But how I can configure pytest in my package such that the default behavior is to skip those tests? Specifically, I have some tests that are very slow (multiple seconds each). I want to mark them 'slow', and have the default behavior when running `pytest` be to skip them. That way they will only run if you explicitly run them with `pytest -m slow`. Is there a way to configure this in conftest.py? -ofer

2 3

[hpk42/pytest-cache] setup.py license (issue #7)
by Andreas Pelme April 9, 2013

April 9, 2013

New issue 7: setup.py license https://bitbucket.org/hpk42/pytest-cache/issue/7/setuppy-license Andreas Pelme: I believe to intended license for pytest-cache is MIT (as per LICENSE), but setup.py says GPL, which also shows on PyPI. The setup.py file should probably be changed. -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue.

1 0