Mailman 3 September 2014 - pytest-dev

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

running py-test setup without actual running the tests and their tear down
by Ayelet Regev Sept. 29, 2014

Sept. 29, 2014

Hi, I wish to allow --validate_only option to my py.test plugin. i want the ability to run many checks without actually running the pytest_runtest_call and pytest_runtest_teardown. What is the best approach? -- Best Regards, Ayelet Regev Dabah Email: ayelet(a)fabrixsystems.com

1 0

Is it valid to use --boxed with --capture=no?
by David Röthlisberger Sept. 29, 2014

Sept. 29, 2014

Is it valid to use --boxed with --capture=no? It fails with UnicodeEncodeError. More details at https://bitbucket.org/hpk42/pytest/issue/573 but I'm asking here since I haven't received an anwer on the bitbucket issue in a month. :-) The reason I want to do that is that I'm looking into using pytest as the test-runner for my (open source) system for testing set-top boxes & TVs, and I need to capture (and timestamp) the std{err,out} logs myself. Some more background on that at http://stb-tester.com/blog/2014/09/25/upcoming-features-new-test-runner.html Thanks, Dave.

2 6

Hook validation difference between conftest files and plugins
by Bruno Oliveira Sept. 29, 2014

Sept. 29, 2014

Hi everyone, I'm having some trouble when trying to use some of xdist-defined hooks in a plugin, but I believe this problem is not related to xdist specifically. If I redefine a few of `xdist`'s hook functions inside a conftest file, it works fine. Once I move them to an external plugin however, I start getting "found unknown hook" errors. Here is an example: # contents of conftest.py def pytest_configure_node(node): assert 0, 'configure_node called' # contents of test_foo.py def test_foo(): pass In a fresh virtual environment with `pytest-xdist` installed: $ py.test -n2 <snip traceback> INTERNALERROR> AssertionError: configure_node called OK, that's what I expected. On the other hand, renaming `conftest.py` to `myplugin.py`: $ py.test -n2 -p myplugin raise PluginValidationError("%s:\n%s" % (name, stringio.getvalue())) _pytest.helpconfig.PluginValidationError: myplugin: found unknown hook: pytest_configure_node (You might have to configure your $PYTHONPATH to the working directory) The same happens if I make a plugin using setup.py/setuptools. Am I missing something, or is this a bug? Digging at the source a bit I found that plugin registration and hook validation happen one right after the other, which might be a problem because a plugin might depend on hooks that will be registered by other plugins later. Cheers, Bruno.

3 3

removed outdated japanese docs
by holger krekel Sept. 29, 2014

Sept. 29, 2014

Hi all, i just removed the japanese documentation because it's just a translation of the english docs a the time of the pytest-2.2 release. So it's more misleading now than helpful. Also i am not convinced a test tool used by software developers should care much for non-english TBH. If you disagree and/or would like to maintain the japanese docs, please tell! There still remain available at http://pytest.org/latest-ja for the time being. best, holger

1 0

top-level conftest.py not recognized when running tests in sub-directories
by Jens Hoffmann Sept. 26, 2014

Sept. 26, 2014

Hi, we are working with pytest 2.6.2 and I run into a problem with my conftest session fixture setup. My project structure looks something like this: . ├── project │ └── module │ └── foo.py └── test ├── conftest.py └── module └── test_foo.py conftest.py contains a single fixture with scope="session" and autouse=True, setting up some database that is needed for every single unittest. So also test_foo.py depends on that database setup. Now some py.test runs: $ py.test => conftest.py called, database setup properly, tests pass $ py.test test/module => tests fail, fixture in conftest.py not executed $ py.test test/module/test_foo.py => tests fail, fixture in conftest.py not executed $ py.test -k MyTestClassContainedInTestFooDotPy => tests fail, fixture in conftest.py not executed Now my question/problem: Are all these outcoms expected behaviour? I hoped that all the runs would pass, that is execute my session fixture so that I wont need to always run my whole test suite. Thank you for your answer, Jens

4 14

tox-1.8: parametrized/generative environments
by holger krekel Sept. 24, 2014

Sept. 24, 2014

tox 1.8: Generative/combinatorial environments specs ============================================================================= I am happy to announce tox 1.8 which implements parametrized environments and should otherwise be fully backward compatible to tox-1.7.2. See https://tox.testrun.org/latest/config.html#generating-environments-conditio… for examples and the new backward compatible syntax in your tox.ini file. Many thanks to Alexander Schepanovski for implementing and refining it based on the specifcation draft. More documentation about tox in general: http://tox.testrun.org/ Installation: pip install -U tox code hosting and issue tracking on bitbucket: https://bitbucket.org/hpk42/tox What is tox? ---------------- tox standardizes and automates tedious test activities driven from a simple ``tox.ini`` file, including: * creation and management of different virtualenv environments with different Python interpreters * packaging and installing your package into each of them * running your test tool of choice, be it nose, py.test or unittest2 or other tools such as "sphinx" doc checks * testing dev packages against each other without needing to upload to PyPI best, Holger Krekel, merlinux GmbH Changes 1.8 (compared to 1.7.2) --------------------------------------- - new multi-dimensional configuration support. Many thanks to Alexander Schepanovski for the complete PR with docs. And to Mike Bayer and others for testing and feedback. - fix issue148: remove "__PYVENV_LAUNCHER__" from os.environ when starting subprocesses. Thanks Steven Myint. - fix issue152: set VIRTUAL_ENV when running test commands, thanks Florian Ludwig. - better report if we can't get version_info from an interpreter executable. Thanks Floris Bruynooghe.

2 1

pytest-2.6.3: some fixes
by holger krekel Sept. 24, 2014

Sept. 24, 2014

pytest-2.6.3: fixes and little improvements =========================================================================== pytest is a mature Python testing tool with more than a 1100 tests against itself, passing on many different interpreters and platforms. This release is drop-in compatible to 2.5.2 and 2.6.X. See below for the changes and see docs at: http://pytest.org As usual, you can upgrade from pypi via:: pip install -U pytest Thanks to all who contributed, among them: Floris Bruynooghe Oleg Sinyavskiy Uwe Schmitt Charles Cloud Wolfgang Schnerring have fun, holger krekel Changes 2.6.3 ====================== - fix issue575: xunit-xml was reporting collection errors as failures instead of errors, thanks Oleg Sinyavskiy. - fix issue582: fix setuptools example, thanks Laszlo Papp and Ronny Pfannschmidt. - Fix infinite recursion bug when pickling capture.EncodedFile, thanks Uwe Schmitt. - fix issue589: fix bad interaction with numpy and others when showing exceptions. Check for precise "maximum recursion depth exceed" exception instead of presuming any RuntimeError is that one (implemented in py dep). Thanks Charles Cloud for analysing the issue. - fix conftest related fixture visibility issue: when running with a CWD outside a test package pytest would get fixture discovery wrong. Thanks to Wolfgang Schnerring for figuring out a reproducable example. - Introduce pytest_enter_pdb hook (needed e.g. by pytest_timeout to cancel the timeout when interactively entering pdb). Thanks Wolfgang Schnerring. - check xfail/skip also with non-python function test items. Thanks Floris Bruynooghe.

1 0

xdist and data sharing during execution in parallel
by Ayelet Regev Sept. 24, 2014

Sept. 24, 2014

Hi, I'm creating a time-line based on pytest. im using xdist with multiple slaves (in the amount of the tests). Each test is started by time and dependency. which mean some of the gateways will be waiting for others to be "Done". for that, io need some data sharing between them all, and cannot use "slaveoutput". i created my own dict object using file handler, and i want to create instance once on master and share it will all slaves. but i cannot pass object to "slaveinput" Do you have any advice? * **def pytest_configure(config):* config.global_time_line_json = config.getoption("timeline",None) unicode_to_ascii(config.global_time_line_json) if config.global_time_line_json is None: raise Exception("no timeline data was provided to command") config.properties = config.getoption("properties") unicode_to_ascii(config.properties) logfile = config.properties.get("logfile",None) if logfile is None: raise Exception("no logfile path was provided to command under properties") config.flow_dir = config.properties.get("flow_dir",None) logfile_basename = os.path.basename(logfile) _logger = Logger(config.flow_dir,logfile_basename) config.logger = _logger.logger() config.active_dir = "%s/%s" % (config.flow_dir,ACTIVE_DIR) *if not hasattr(config,"slaveinput"):** ** config.logger.info2("Master")** ** config.global_data = PersistentDict('%s/%s' % (config.active_dir,FLOW_JSON), 'c', format='json')* *def pytest_configure_node(node):* # runs only on Master node.config.logger.info2("on Master sending data to Slave") *node.slaveinput["global_data"] = node.config.global_data* -- Best Regards, Ayelet Regev Dabah Email: ayelet(a)fabrixsystems.com

3 2

pytest-xdist-1.11: restarting crash nodes, fixture cache fix
by holger krekel Sept. 23, 2014

Sept. 23, 2014

I just released pytest-xdist-1.11, the distributed testing plugin for pytest. It introduces automatic restarting of crashed nodes, courtesy of a complete PR from Floris Bruynooghe. This also works well together with pytest-timeout by the same author: When one or more test functions hang or crash, the overall test run will still complete and report about the incidents. See the changelog below for more changes and the pypi project page for what pytest-xdist offers in general: https://pypi.python.org/pypi/pytest-xdist/ Thanks also to an undisclosed company who partly funded the work and to Andreas Pelme for contributing analysis of a fixture caching failure including a test. best, Holger Krekel 1.11 ------------------------- - fix pytest/xdist issue485 (also depends on py-1.4.22): attach stdout/stderr on --boxed processes that die. - fix pytest/xdist issue503: make sure that a node has usually two items to execute to avoid scoped fixtures to be torn down pre-maturely (fixture teardown/setup is "nextitem" sensitive). Thanks to Andreas Pelme for bug analysis and failing test. - restart crashed nodes by internally refactoring setup handling of nodes. Also includes better code documentation. Many thanks to Floris Bruynooghe for the complete PR.

3 16