Mailman 3 December 2013 - pytest-dev

Autocompletion on fixture objects as test function input arguments - PyCharm
by Michelle Chartier Jan. 14, 2014

Jan. 14, 2014

Hey all, I recently got the community edition PyCharm IDE and so far like a lot of things about it (especially the ability to run pytest tests from within it). HOWEVER, I am having a problem with auto-completion on fixture functions (I realize this may not be the place to ask this question but I was hoping someone had some info that could help me or point me somewhere :) ) So, the problem: in my test function I am using a fixture object as an input argument and want to be able to see all available functions with autocompletion. To see autocompletion in Aptana, I imported the necessary fixture to the test module where my test function resides (the fixture is imported to a conftest in a package I have defined) ---------------------------------- Example: #this test module resides in mypackag.mysubpackage.mysubsubpackage from mypackage.mysubpackage.conftest import myobj def test_mytest(myobj): myobj. (<- this is where the autocompletion should show up?) ---------------------------------- In Aptana myobj shows all the available functions with autocompletion as expected but in PyCharm (with the exact same code/folders/folder structure) it says "No suggestions." Anyone have a similar problem or know of a solution? (I would prefer to stick with PyCharm... :) ) Thanks! Michelle

3 2

How to determinate if test is skipped on runtest_teardown hook?
by Anton P Jan. 6, 2014

Jan. 6, 2014

Hi All, Is there is possibility to determinate if test is skipped or not on pytest_runtest_teardown hook. I can see skipif marker in item.keywords, but I don't know it's status. Thank you in advance! Anton

2 3

pytest-2.5.1: fixes and new home page styling
by holger krekel Dec. 18, 2013

Dec. 18, 2013

pytest-2.5.1: fixes and new home page styling =========================================================================== pytest is a mature Python testing tool with more than a 1000 tests against itself, passing on many different interpreters and platforms. The 2.5.1 release maintains the "zero-reported-bugs" promise by fixing the three bugs reported since the last release a few days ago. It also features a new home page styling implemented by Tobias Bieniek, based on the flask theme from Armin Ronacher: http://pytest.org If you have anything more to improve styling and docs, we'd be very happy to merge further pull requests. On the coding side, the release also contains a little enhancement to fixture decorators allowing to directly influence generation of test ids, thanks to Floris Bruynooghe. Other thanks for helping with this release go to Anatoly Bubenkoff and Ronny Pfannschmidt. As usual, you can upgrade from pypi via:: pip install -U pytest have fun and a nice remaining "bug-free" time of the year :) holger krekel 2.5.1 ----------------------------------- - merge new documentation styling PR from Tobias Bieniek. - fix issue403: allow parametrize of multiple same-name functions within a collection node. Thanks Andreas Kloeckner and Alex Gaynor for reporting and analysis. - Allow parameterized fixtures to specify the ID of the parameters by adding an ids argument to pytest.fixture() and pytest.yield_fixture(). Thanks Floris Bruynooghe. - fix issue404 by always using the binary xml escape in the junitxml plugin. Thanks Ronny Pfannschmidt. - fix issue407: fix addoption docstring to point to argparse instead of optparse. Thanks Daniel D. Wright.

2 2

Re: [pytest-dev] regarding parametrized ids
by Floris Bruynooghe Dec. 16, 2013

Dec. 16, 2013

Hello Holger, On 16 December 2013 05:31, holger krekel <holger(a)merlinux.eu> wrote: > Hi Floris, > > i think the docstring is wrong: "argvalues" is not part of @fixture signature. Oops, copied that from MetaFunc.parameterize(). Fixed it to refer to params. > Btw, Anatoly suggests even core committers (including me) should propose > PRs instead of committing directly for any non-trivial change. I'd like > to try this out for a while (probably hardest for me :). What do you think? I'm all for giving this a go. But maybe we'd want to discuss some workflow on pytest-dev, e.g. what branching style to use etc. Personally I like mq but bitbucket's support for it is a bit poor (no pull requests). So far I've just created a throw-away repo per pull request to avoid creating branches but that gets a bit cumbersome I guess. What would also be great is if we could aromatically have the full tox tests run for each pull request, maybe this is possible with some devpi interaction? Or this is already possible with the travis setup (but I thought that had incomplete coverage)? I'm happy to try and help towards this and I'm pretty sure we can help donate a vm to run tests on (we already have a cpython buildslave running on sparc), or we might be able to get some rackspace dontated boxes (I heard they do this for free software projects and they'll have better connectivity)? Regards, Floris -- Debian GNU/Linux -- The Power of Freedom www.debian.org | www.gnu.org | www.kernel.org

1 0

new pytest docs styling PR
by holger krekel Dec. 14, 2013

Dec. 14, 2013

Hi all, Tobias Bieniek offered a Pull Request for a new pytest doc styling. He includes a few screenshots: https://github.com/hpk42/pytest/pull/8 What do you think? best, holger

3 4

pytest-2.5.0: many fixes. ZERO reported bugs left.
by holger krekel Dec. 12, 2013

Dec. 12, 2013

pytest-2.5.0: many fixes ... now down to ZERO reported bugs! =========================================================================== pytest-2.5.0 is a big bug fixing release, the result of two community bug fixing days plus numerous additional works from many people and reporters. The release should be fully compatible to 2.4.2, existing plugins and test suites. We aim at maintaining this level of ZERO reported bugs because it's no fun if your testing tool has bugs, is it? Under a condition, though: when submitting a bug report please provide clear information about the circumstances and a simple example which reproduces the problem. The issue tracker is of course not empty now. We have many remaining "enhancement" issues which we'll hopefully can tackle in 2014 with your help. For those who use older Python versions, please note that pytest is itself not automatically tested anymore on python2.5 due to virtualenv, setuptools and tox not supporting it anymore. Manual verification shows that it works fine still but that might change in the future. As usual, current docs are at http://pytest.org and you can upgrade from pypi via:: pip install -U pytest Particular thanks for helping with this release go to Anatoly Bubenkoff, Floris Bruynooghe, Marc Abramowitz, Ralph Schmitt, Ronny Pfannschmidt, Donald Stufft, James Lan, Rob Dennis, Jason R. Coombs, Mathieu Agopian, Virgil Dupras, Bruno Oliveira, Alex Gaynor and others. have fun, holger krekel 2.5.0 ----------------------------------- - dropped python2.5 from automated release testing of pytest itself which means it's probably going to break soon (but still works with this release we believe). - simplified and fixed implementation for calling finalizers when parametrized fixtures or function arguments are involved. finalization is now performed lazily at setup time instead of in the "teardown phase". While this might sound odd at first, it helps to ensure that we are correctly handling setup/teardown even in complex code. User-level code should not be affected unless it's implementing the pytest_runtest_teardown hook and expecting certain fixture instances are torn down within (very unlikely and would have been unreliable anyway). - PR90: add --color=yes|no|auto option to force terminal coloring mode ("auto" is default). Thanks Marc Abramowitz. - fix issue319 - correctly show unicode in assertion errors. Many thanks to Floris Bruynooghe for the complete PR. Also means we depend on py>=1.4.19 now. - fix issue396 - correctly sort and finalize class-scoped parametrized tests independently from number of methods on the class. - refix issue323 in a better way -- parametrization should now never cause Runtime Recursion errors because the underlying algorithm for re-ordering tests per-scope/per-fixture is not recursive anymore (it was tail-call recursive before which could lead to problems for more than >966 non-function scoped parameters). - fix issue290 - there is preliminary support now for parametrizing with repeated same values (sometimes useful to to test if calling a second time works as with the first time). - close issue240 - document precisely how pytest module importing works, discuss the two common test directory layouts, and how it interacts with PEP420-namespace packages. - fix issue246 fix finalizer order to be LIFO on independent fixtures depending on a parametrized higher-than-function scoped fixture. (was quite some effort so please bear with the complexity of this sentence :) Thanks Ralph Schmitt for the precise failure example. - fix issue244 by implementing special index for parameters to only use indices for paramentrized test ids - fix issue287 by running all finalizers but saving the exception from the first failing finalizer and re-raising it so teardown will still have failed. We reraise the first failing exception because it might be the cause for other finalizers to fail. - fix ordering when mock.patch or other standard decorator-wrappings are used with test methods. This fixues issue346 and should help with random "xdist" collection failures. Thanks to Ronny Pfannschmidt and Donald Stufft for helping to isolate it. - fix issue357 - special case "-k" expressions to allow for filtering with simple strings that are not valid python expressions. Examples: "-k 1.3" matches all tests parametrized with 1.3. "-k None" filters all tests that have "None" in their name and conversely "-k 'not None'". Previously these examples would raise syntax errors. - fix issue384 by removing the trial support code since the unittest compat enhancements allow trial to handle it on its own - don't hide an ImportError when importing a plugin produces one. fixes issue375. - fix issue275 - allow usefixtures and autouse fixtures for running doctest text files. - fix issue380 by making --resultlog only rely on longrepr instead of the "reprcrash" attribute which only exists sometimes. - address issue122: allow @pytest.fixture(params=iterator) by exploding into a list early on. - fix pexpect-3.0 compatibility for pytest's own tests. (fixes issue386) - allow nested parametrize-value markers, thanks James Lan for the PR. - fix unicode handling with new monkeypatch.setattr(import_path, value) API. Thanks Rob Dennis. Fixes issue371. - fix unicode handling with junitxml, fixes issue368. - In assertion rewriting mode on Python 2, fix the detection of coding cookies. See issue #330. - make "--runxfail" turn imperative pytest.xfail calls into no ops (it already did neutralize pytest.mark.xfail markers) - refine pytest / pkg_resources interactions: The AssertionRewritingHook PEP302 compliant loader now registers itself with setuptools/pkg_resources properly so that the pkg_resources.resource_stream method works properly. Fixes issue366. Thanks for the investigations and full PR to Jason R. Coombs. - pytestconfig fixture is now session-scoped as it is the same object during the whole test run. Fixes issue370. - avoid one surprising case of marker malfunction/confusion:: @pytest.mark.some(lambda arg: ...) def test_function(): would not work correctly because pytest assumes @pytest.mark.some gets a function to be decorated already. We now at least detect if this arg is an lambda and thus the example will work. Thanks Alex Gaynor for bringing it up. - xfail a test on pypy that checks wrong encoding/ascii (pypy does not error out). fixes issue385. - internally make varnames() deal with classes's __init__, although it's not needed by pytest itself atm. Also fix caching. Fixes issue376. - fix issue221 - handle importing of namespace-package with no __init__.py properly. - refactor internal FixtureRequest handling to avoid monkeypatching. One of the positive user-facing effects is that the "request" object can now be used in closures. - fixed version comparison in pytest.importskip(modname, minverstring) - fix issue377 by clarifying in the nose-compat docs that pytest does not duplicate the unittest-API into the "plain" namespace. - fix verbose reporting for @mock'd test functions

1 0

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

Dec. 11, 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