Mailman 3 January 2015 - pytest-dev

Crowdfunding a pytest plugin
by Tibor Arpas March 13, 2015

March 13, 2015

Hello pytesters, We are putting together a small Indiegogo campaign for a pytest plugin which should significantly improve the experience of executing a long test suite. We'd be glad to hear any feedback before launching it. The draft is here: https://www.indiegogo.com/project/preview/4fe07d66 Also, is anybody interested in helping with promotion and/or development? Cheers, Tibor

4 6

Enabling viewing of rewritten AST trees as Python
by Tom Viner March 2, 2015

March 2, 2015

Hi, In the process of fixing a recent bug <https://bitbucket.org/hpk42/pytest/issue/615/valueerror-on-compound-assert-…> in pytest source rewriting I found a library to take the rewritten AST tree and generate Python source code from it. Floris mentioned this could be helpful to pytest developers working on the assertion rewriting code. The library is called Meta <https://pypi.python.org/pypi/meta>. (Note, currently only the develop branch on github works successfully on pytest's rewrite tests.) It allows viewing an AST tree as Python source with a single call: import meta log.debug(meta.asttools.dump_python_source(ast_tree)) The question I have: how can pytest developers (and those debugging pytest's rewriting of their tests) best get access to the rewritten AST tree, to be able to view it's Python source representation? The AST tree is seen in pytest/_pytest/assertion/rewrite.py::rewrite_asserts <https://bitbucket.org/hpk42/pytest/src/default/_pytest/assertion/rewrite.py…> in the mod variable: def rewrite_asserts(mod): """Rewrite the assert statements in mod.""" AssertionRewriter().run(mod) The four options I can think of to gain access to this variable: - monkey patch rewrite.rewrite_asserts - edit rewrite_asserts and paste in the logging code above: -- temporarily, by each developer, on each occasion required -- permanently, but only running when a certain debug flag is active - expose the rewritten AST via a new hook monkey patch is my preferred option, because if I can make it work, a plugin could be written. I just need some help to find an appropriate hook to do the monkey patching before pytest gets going with the AssertionRewritingHook and calls rewrite_asserts. Without knowledge of an early-running hook, I could only get this working by patching rewrite_asserts then calling pytest.main myself, see https://gist.github.com/tomviner/13c95cdb1e159028fc0b Second option, I could explain how to do the temporary edit in a short blog post. This would get past the pytest.main downside to the gist above. But telling people to edit random pytest source files seems bad form. Third option, a pull request on pytest logging the Python source, only if a debug flag is active and Meta is importable. But is this reasonable just for debugging purposes? Alternatively, fourth, a new hook could be added to expose the rewritten AST tree, and everything else could then be a plugin. Thoughts? To see the assertion rewriting pytest does, as Python code, follow the instructions in my gist: https://gist.github.com/tomviner/13c95cdb1e159028fc0b Cheers, Tom

2 3

FOSDEM / Saturday pytest meetup in Bruxelles
by holger krekel Feb. 1, 2015

Feb. 1, 2015

Hi folks, as some of you know some pytest devs are going to meet at FOSDEM in Bruxelles end of the month. ASFAIK, Anatoly Bubenkoff, Brianna Laugher, Floris Bruynooghe and me are bound to come, anyone else? During our meetup i'd like to discuss and work on finalizing https://bitbucket.org/pytest-dev as the new place for pytest core, py, pytest-xdist, pytest-cache, ..., tox, repositories and using a unified contribution process for all of them. I'd also like to discuss going for a little crowd-funding project that automates testing and releasing pytest-dev packages including pushing docs to the respective sites. Bruno Oliveira has already done some work for visualizing the pytest-plugin status against the latest pytest release which can probably be re-used http://pytest.org/latest/plugins_index/index.html As to the location at FOSDEM, I suggest to meetup 4pm around the Python FOSDEM room: http://python-fosdem.org/#location I'll probably be there during the day but also have some other appointments so can't guarantee that. I'll arrive friday evening but will probably directly go to Pieter Hintjens's flat and only arrive saturday morning at the conf site. best, holger

4 5

pytest github organization is taken
by Anatoly Bubenkov Jan. 29, 2015

Jan. 29, 2015

Hi all if it was you who created this org https://github.com/pytest please make Holger an admin if this name was taken by someone who's not related to pytest in any way, then we should make a claim to github to get the rights i guess the org is empty and created Oct 21, 2013 -- Anatoly Bubenkov

3 5

pytest script sample
by Abdelillah Asraoui Jan. 27, 2015

Jan. 27, 2015

Hello All, I'm a newbie to pytest, would like to get minimum setup of files in pytest: + lib +config file for testbed +test script to do the following tasks : 1. ssh to a linux machine 2. run some linux commands Can someone point out an example where i can take a look at this.. Thanks in Advance, Abdelillah

3 3

fail on zero tests found
by Boris Ribalkin Jan. 21, 2015

Jan. 21, 2015

Is it possible to implement this in py.test: https://bitbucket.org/hpk42/pytest/issue/662/fail-on-zero-tests-found Basically fail by default if pytest cannot find any test, no good anyway :) Thanks -- Boris Rybalkin ribalkin(a)gmail.com

2 1

Automatically converting unittest asserts to py.test asserts.
by Cesar Canassa Jan. 19, 2015

Jan. 19, 2015

Hi, In my current company, I recently switched from using Unittest to Py.test in our Flask application. I loved Py.test and I decided to start rewriting our tests using Py.test style asserts instead of Unittest asserts (self.assertEqual, self.assertFalse, et al). Since we have already written hundreds of thousands of lines of test code, manually converting the tests would take too long, so I have decided to automate the process. The automation effort resulted in this script: https://gist.github.com/canassa/4fd63d682d90f5e3f07e The script is not perfect, you still need to manually review some changes it makes, but at least in our project it worked amazingly well, so I decided to share it with you. Best, Cesar Canassa

2 2

Fixtures not being found when module is named "conftest"
by Bruno Oliveira Jan. 19, 2015

Jan. 19, 2015

Hi everyone! Suppose the following files: # foo/conftest.py import pytest @pytest.fixture def my_fixture(): return 1 # foo/__init__.py <empty file> # bar/conftest.py pytest_plugins = ['foo.conftest'] # bar/test_bar.py def test_it(my_fixture): assert my_fixture == 1 Supposing your PYTHONPATH is configured so you can import "foo.conftest", running "py.test bar" fails because it does not find "my_fixture". However, if you rename "foo/conftest.py" to something else like "foo/plugin.py" and update the reference in "bar/conftest.py", then pytest is able to find "my_fixture". Looking at the code, I see that there is a special case for "conftest.py" files in _pytest.python, line 1617. I was wondering what is the rationale behind this? I was under the impression that "conftest.py" files where simply plugins which were loaded automatically based on their relative location to the tests. In my case, I would like to reuse fixtures defined in conftest files between different projects. For instance, project2 depends on project1's fixtures which are defined in a conftest file, so I would like to simply add a "pytest_plugins = ['project1.conftest']" to project2's own conftest file. If I understand correctly, I would have to move project1's fixture to a different file, say "project1.plugin", and reference it in both project1 and project2's conftest files. Is this the recommended approach? Cheers, Bruno

2 2

pytest-cloud
by Anatoly Bubenkov Jan. 17, 2015

Jan. 17, 2015

Hi i drafted a simple plugin (you can look at it as a subplugin of pytest-xdist) which allows you to automatically choose test nodes and the number of tests per node depending on the node capabilities. It was a bit tricky to choose those parameters before, i hope not anymore with pytest-cloud. Probably can be merged into pytest-xdist later on. https://github.com/pytest-dev/pytest-cloud Any feedback is more than welcome. -- Anatoly Bubenkov

1 0