Mailman 3 April 2015 - pytest-dev

Working with other dependency injection systems
by Kai Groner Sept. 10, 2015

Sept. 10, 2015

Hi testing people! I'm trying to figure out how I can test a code base that uses an existing dependency injection system. I've run into two problems, and I have solutions for each of them but I think maybe there is a better way, so I'm looking for some advice. The first problem is how do I override how a test using this injector is called? I think I want to use the pytest_runtest_call hook, but it still tries to invoke the test without the injector. My current solution is to use the experimental hookwrapper mechanism to replace item.obj with a partially bound version, then restore it afterward. The second problem I'm having is the py.test fixture system is trying to resolve arguments that are provided by this other injector. How can I tell it that some of these don't need to be provided? My current solution is to blind py.test with a wrapper function with a *a, **kw signature. I use functools.wraps, so annotations are introspectable for the other injector, and delete the __wrapped__ attribute to prevent py.test from introspecting it. Is there a nicer, and perhaps less blunt, way to influence the funcarg fixture behaviors? I've tried a couple things with the pytest_collection_modifyitems hook, but haven't gotten anything that works yet. Other details to know about this injection system: - we want to build and teardown the injector with each test - we may want to configure the injector differently for some tests (possibly with fixture data from py.test) Thanks, Kai

2 6

Re: [pytest-dev] Pytest-asyncio
by Laura Creighton April 23, 2015

April 23, 2015

In a message of Thu, 23 Apr 2015 21:28:52 +0200, Tin Tvrtković writes: >Hello fellow pytest aficionados, > >I've been advised by multiple people over Twitter to bring this to the >attention of the pytest community, so here goes. > >I'm the author of pytest-asyncio, a pytest plugin for testing asyncio >code: https://github.com/Tinche/pytest-asyncio. The code isn't >particularly clever, and could use a review by someone more >knowledgeable of pytest than me, but it seems to do its job okay (I'm >already using it in another asyncio project). Credit where credit is >due: the plugin is basically a port of pytest-tornado to asyncio. It's >up on PyPI under the name 'pytest-asyncio'. Hopefully the README file is >documentation enough. > >It's also been suggested to me to submit the plugin to pytest, which I'd >totally be open to if you folks are interested. I think the plugin ticks >all the checkboxes listed on https://pytest.org/latest/contributing.html. > >Kind regards, >Tin I've been using it, for about a week. It is working great here. so +1 from me. Laura

2 1

Pytest-asyncio
by Tin Tvrtković April 23, 2015

April 23, 2015

Hello fellow pytest aficionados, I've been advised by multiple people over Twitter to bring this to the attention of the pytest community, so here goes. I'm the author of pytest-asyncio, a pytest plugin for testing asyncio code: https://github.com/Tinche/pytest-asyncio. The code isn't particularly clever, and could use a review by someone more knowledgeable of pytest than me, but it seems to do its job okay (I'm already using it in another asyncio project). Credit where credit is due: the plugin is basically a port of pytest-tornado to asyncio. It's up on PyPI under the name 'pytest-asyncio'. Hopefully the README file is documentation enough. It's also been suggested to me to submit the plugin to pytest, which I'd totally be open to if you folks are interested. I think the plugin ticks all the checkboxes listed on https://pytest.org/latest/contributing.html. Kind regards, Tin

1 0

Re: [pytest-dev] Pytest + Doctest + Tox
by Sravan Bhamidipati April 21, 2015

April 21, 2015

On Mon, Apr 20, 2015 at 7:20 PM, <pytest-dev-request(a)python.org> wrote: > It seems that ``setup.py`` is collected, not protected by > ``if __name__ == "__main__":`` and thus executes during collection > as a side effect of importing it. > > You could add the protection which should suffice. > You could also add "--ignore=setup.py" to to the pytest invocation > (possibly also via the "addopts" config variable). > Thank you, Holger. I started using addopts, and it solved both the setup.py error as well as the slow discovery of doctests.

1 0

EP2015 -- Bilbao CFP ends today
by holger krekel April 20, 2015

April 20, 2015

Hey Floris, Brianna, Ronny, Anatoly, Andreas, all, Today the CFP for EP2015 in Bilbao ends. Did you submit talks? I am pondering something pytest or tox or devpi related, maybe a training. I'd like to make sure we don't overlap too much or even complement each other. best, holger

7 10

pytest-2.7.1 / bugs? / release?
by holger krekel April 20, 2015

April 20, 2015

Hi all, what about we try to do a little pytest-2.7.1 release in like 10 days or so? Two suggestions for that: - everyone picks and fixes (at least) one bug within the next 7 days (everyone == (committers + anyone) willing to help) - someone other than me does the release (i'll be around to help if questions arise) according to doc/en/release.txt Meanwhile i am working on adding wheel support to "devpi test" so that we can publish wheels as well, including for the "py" dependency. That should hopefully land next week as it experimentally works already. best, holger -- about me: http://holgerkrekel.net/about-me/ contracting: http://merlinux.eu

4 3

Pytest + Doctest + Tox
by Sravan Bhamidipati April 20, 2015

April 20, 2015

Hello pytesters, I am trying to get guessit <https://github.com/bsravanin/guessit> to adopt pytest this month. It uses tox. When I try to run the tests with the "--doctest-modules" option, the tests are being discovered as expected, but the run fails with the following error: ========================================================================== > ERRORS > ========================================================================== > ________________________________________________________________ ERROR > collecting setup.py > _________________________________________________________________ > setup.py:109: in <module> > setup(**args) > /usr/local/Cellar/python/2.7.9/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/core.py:139: > in setup > raise SystemExit, gen_usage(dist.script_name) + "\nerror: %s" % msg > E SystemExit: usage: py.test [global_opts] cmd1 [cmd1_opts] [cmd2 > [cmd2_opts] ...] > E or: py.test --help [cmd1 cmd2 ...] > E or: py.test --help-commands > E or: py.test cmd --help > E > E error: option --doctest-modules not recognized > =========================================================== 46 passed, 1 > error in 15.08 seconds > ============================================================ You can checkout this commit <https://github.com/bsravanin/guessit/commit/01b0de3bb52a4c8fced49f5feb0c67a…> to see what's going on. If you need any more information, please let me know. There is a second problem. When I try to run "py.test --doctest-modules" after activating the virtualenv (source .tox/py27/bin/activate, e.g.), the doctests are being discovered immediately. But when I try to run them as part of the tox command (which runs "python setup.py test" which in turn uses a TestCommand to run pytests), the discover of doctests is taking about 15s. It would be nice to be able to also fix that. I searched StackOverflow, but there're quite a few pytest-doctest questions there that have been unanswered, so I'm emailing this list directly. Regards, Sravan

2 1

New plugin for generating HTML report (and request for help)
by Dave Hunt April 20, 2015

April 20, 2015

Hey py.testers! I’ve been working on pulling a feature out of our pytest-mozwebqa plugin into a standalone plugin. I think others may find it useful, and it would simplify maintenance of the former plugin to split this out. Please take a look over the pytest-html plugin, the source code is available here: https://github.com/davehunt/pytest-html <https://github.com/davehunt/pytest-html> Basically this plugin provides a new command line option of —html which allows the user to specify a path for a HTML report to be generated. The report can then be enhanced by adding extra components via the pytest_runtest_makereport hook. You can see an example of this in my in-progress branch of pytest-mozwebqa where I’ve switched to using the new plugin: https://github.com/davehunt/pytest-mozwebqa/blob/1074f0770a146cff3108191a2f… <https://github.com/davehunt/pytest-mozwebqa/blob/1074f0770a146cff3108191a2f…> What I’d like some help with is providing the HTML report with environment details. This is essentially just a dictionary that will be included in the HTML report, but should be optionally provided by another plugin or conftest.py file. At the moment I accept an environment keyword argument when instantiating the HTMLReport object, but I’m not aware of a way to influence this from another plugin. See: https://github.com/davehunt/pytest-html/blob/752f229b990c80e66195374a4ed4fe… <https://github.com/davehunt/pytest-html/blob/752f229b990c80e66195374a4ed4fe…> and https://github.com/davehunt/pytest-html/blob/752f229b990c80e66195374a4ed4fe… <https://github.com/davehunt/pytest-html/blob/752f229b990c80e66195374a4ed4fe…> If anybody has any advice it would be much appreciated! Thanks in advance, -- Dave Hunt Automation Engineer Mozilla Corporation dhunt(a)mozilla.com

3 4

code coverage of tests using pytester - testdir.runpytest
by Eduardo Schettino April 20, 2015

April 20, 2015

Hi, I am using the pytester plugin to test my own plugin. It works ok but I can not get code coverage because testdir.runpytest uses os.popen(). Have anyone managed to work around that? Can you point me to a project/plugin that handles that? cheers, Eduardo

4 7

code coverage of tests using pytester - testdir.runpytest
by Tibor Arpas April 17, 2015

April 17, 2015

Hi, have you tried http://nedbatchelder.com/code/coverage/subprocess.html ? It works for me. Also pytest-cov plugin advertises it supports measuring subprocesses. And testdir.inline_run() exists, in case you didn't spot it. That doesn't use popen so coverage is recorded just fine. The downside of inline_run for me was that I coudln't get the stdout of the execution. Tibor On Fri, Apr 17, 2015 at 8:39 PM Eduardo Schettino <schettino72(a)gmail.com> wrote: > Hi, > > I am using the pytester plugin to test my own plugin. > > It works ok but I can not get code coverage because testdir.runpytest uses > os.popen(). > Have anyone managed to work around that? Can you point me to a > project/plugin that handles that? > > cheers, > Eduardo > _______________________________________________ > pytest-dev mailing list > pytest-dev(a)python.org > https://mail.python.org/mailman/listinfo/pytest-dev >

1 0