Mailman 3 November 2013 - pytest-dev

fixtures and pylint W0621
by Brianna Laugher Dec. 10, 2013

Dec. 10, 2013

Hi, Defining a fixture in the same file as a test that uses it triggers a pylint complaint: "W0621:*Redefining name %r from outer scope (line %s)* Used when a variable’s name hide a name defined in the outer scope." If the fixture was in conftest.py it would be fine. But it is nice to have fixtures in the same file if they are only used there. Does everybody just disable this message? I find it useful in general, I would prefer not to disable it completely. thanks Brianna -- They've just been waiting in a mountain for the right moment: http://modernthings.org/

4 13

Question about silencing pytest xdist plugin reporting
by Lenni Kuff Nov. 23, 2013

Nov. 23, 2013

Hi, I am experimenting with using Pytest + Xdist and I was wondering if it is possible to completely/mostly silence the xdist logging? When running many tests in parallel there can be a lots of spew like: gw0 C / gw1 I / gw2 I / gw3 I / gw4 I / gw5 I / gw6 I / gw7 I / gw8 I / gw9 I / gw10 I / gw11 I / gw12 I / gw13 gw0 C / gw1 C ... I have been able to reduce the output a bit by adding the following into by conftest.py file, but can't figure out how to completely silence the output: def pytest_xdist_setupnodes(config, specs): config.option.verbose = 0 Any help would be appreciated. Thanks, Lenni

2 1

Running finalizer in case test setup has failed
by Andrii Smirnov Nov. 20, 2013

Nov. 20, 2013

Hello All, We have complex enough (several stages of putting the test environment into some condition) code which should be executed in all cases regardless of test setup result (fixture setup). Since finalizer for fixture will not be called in case its (fixture) setup failed we've put some calls to pytest_sessionfinish as a temporary workaround but we need to find a way how to call finalizer code explicitly. Could you please suggest how to achieve that? Thank you in advance! -Andrii

3 3

Calling pytest.main() does not pick up changes made to test script file
by achartier＠fastmail.fm Nov. 19, 2013

Nov. 19, 2013

Hello, We are developing an in-house testing tool based on pytest and are interested in calling pytest programmatically using pytest.main(). Unfortunately, using this approach, pytest does not "see" changes I make to my pytest test script file between successive calls to pytest.main(). For example, I have a pytest test script called "testscript.py". This test script file currently has one test called "test_1". If I call pytest.main("testscript.py") it correctly runs the one "test_1" test. If I now change the testscript.py file to include, for instance, the definition of another test (called "test_2") and run pytest.main("testscript.py") it does not see test_2 but only shows test_1. In order for pytest to see test_2, I must shut down the Python terminal, open a new Python terminal and then call pytest.main() again. This workflow is unfortunately not acceptable for our use case. Does pytest have some file caching mechanism that is causing this issue? Is there a pytest configuration option I am missing that can fix this? Am I doing anything wrong? Any help in this regard is greatly appreciated. Thank you, Alfonso

1 0

pytest bug day tomorrow / stackoverflow / bitbucket
by holger krekel Nov. 18, 2013

Nov. 18, 2013

Hi all, 1. tomorrow is pytest bug day. I'll be online 9am CET on IRC #pylib and hope to be there for most of the day and some in the evening. We'll do a little etherpad and list issues and who works on what. 2. I'd be very happy if you subscribed to Stackoverflow's "pytest" tag as to receive notifications when people ask questions about pytest and for upvoting/commenting on questions and answers: http://stackoverflow.com/questions/tagged/py.test 3. Lastly, and this costs you only 30 seconds once, it would help me and others if you upvoted this general bitbucket feature issue: https://bitbucket.org/site/master/issue/7949/ It would mean maintainers can safe time by subscribing to all issues of a project wholesale, without having to explicitely do it for each issue. cheers and thanks! holger

1 0

Pytest (2.3.3) is not taking arguments on windows-Please help
by Dhruv Bhagi Nov. 15, 2013

Nov. 15, 2013

Hi, I'm relatively new to using pytest on windows. I have bunch of test files (like test1.py, test2.py, test3.py etc in a folder tests). The goal is to run a particular individual test <say test1.py>by running the command 'pytest test1.py'. Instead, pytest is running all the tests in the 'tests' folder <rather than running only test1.py>. pytest is not even any arguments <like --version, --help etc.>. If i do 'pytest --version', it still runs all the tests in the folder. So the problem is, pytest not parsing/taking any arguments supplied to it. This is happening only on windows (i'm using windows7, pytest 2.3.3). Anyone seen this before? What could be possibly wrong? (Or) what part of the pytest code should i look at to drill down to the problem? Please advise. I'm kinda blocked by this. I will be greatly thankful for your help. Thanks in advance, Dhruv

2 2

pytest bugday: TUESDAY, 19th november 2013
by holger krekel Nov. 14, 2013

Nov. 14, 2013

Hi all, pytest bug day is final: Tuesday, 19th November starting 9AM UTC+1 on #pylib freenode Let's see to package a pytest-2.4.3 containing the work of the bug/issue-fixing day later in that week. cheers, holger

1 0

plugin status page
by holger krekel Nov. 14, 2013

Nov. 14, 2013

Hi Bruno, all, i've brought your initial work online at the "dev" pytest pages: http://pytest.org/dev/plugins_index.html I think it's a good start, thanks! My comments and wishes (others may comment as well!): - i'd collapse NAME and VERSION columns to save space, i.e. "pytest-bdd-0.6.1". - we should try to collect repository locations. maybe parsing for github/bitbucket urls would yield most of them automatically? Maybe we need to add some manually. - what about adding download numbers? - as to code organisation: you can leave it as is for now or (maybe better) put all code and generated files into a dedicated directory. A very interesting bit will be the "2.4.2 compat" and "dev" compat determination. In fact, i think "devpi" should help with that although i guess i need to improve some things. You can give using it a try with these steps: pip install devpi-client devpi use http://devpi.net/root/pypi devpi test -e py27 pytest-pep8 The last bit should download the pypi-version of pytest-pep8, unpack it and run tox for the "py27" environment and then post back test results (as a json file) to the devpi.net server. You can also ask about plugin "test" status: devpi list pytest-pep8 I just found out that this doesn't work for "pytest-flakes" yet although that does have a tox.ini. need to look into what's going on. In principle, devpi-server (an instance of which you are using above), provides a lot of detailed test info as a json, see here for example: http://devpi.net/+tests/6199353734615fde47d1fbfef1ebc737/toxresult The test results are stored as per the package MD5 at the moment. The whole test/list/json machinery of devpi needs some more work to become really nice, but it should already help as currently implemented, maybe best by using "devpi list" and filing feature requests against it :) For testing "development" versions, it should be enough to upload e.g. a "pytest-2.4.3.dev1" to a private index and then re-run the script that invokes something like the above devpi commands for all of the plugins. Now, for the plugins that don't have a tox.ini we could supply one out of band. For this "devpi test" would grow an option like "--toxini=mytox.ini" and would use that instead of expecting one in the downloaded unpacked distribution file. This tox.ini would probably just have a testenv that does "py.test --version" and "py.test --help" to see if something broke by just installing the plugin. So much for now, holger

3 23

next pytest bug day (doodle)
by holger krekel Nov. 2, 2013

Nov. 2, 2013

Hi all, here is a doodle for arranging for the next pytest bug day. Please list yourself on the days you could at least partially participate: http://doodle.com/dz4nk5q4arib8y97 I am going to pick and announce the final day with the most participants. best, holger

1 0