Mailman 3 October 2018 - pytest-dev

pytest 3.9.3
by Bruno Oliveira Oct. 27, 2018

Oct. 27, 2018

Hi everyone, pytest 3.9.3 has just been released to PyPI. This is a bug-fix release, being a drop-in replacement. To upgrade:: pip install --upgrade pytest The full changelog is available at https://docs.pytest.org/en/latest/changelog.html. Thanks to all who contributed to this release, among them: * Andreas Profous * Ankit Goel * Anthony Sottile * Bruno Oliveira * Daniel Hahler * Jon Dufresne * Ronny Pfannschmidt Happy testing, The pytest Development Team

1 0

Enable "WIP" application in pytest
by Bruno Oliveira Oct. 24, 2018

Oct. 24, 2018

Hi everyone, We often have PRs that are a WIP and should not be merged. I was thinking of enabling the WIP application (https://github.com/apps/wip) for pytest-dev/pytest and see if it is useful. Any thoughts? If nobody raises concerns I intend to enable this tomorrow. :) Cheers, Bruno

2 1

fixture scope wrapping parametrizations
by Brian Okken Oct. 23, 2018

Oct. 23, 2018

Hi, Is there a way to get a fixture scope such that it runs setup before the first parametrization of a test and teardown after the last parametrization? Best I've come up with so far is putting each test into a class and using a class scope fixture. But it seems like a hack. Thanks, Brian Okken

1 0

Deprecation warnings that I didn't cause. Or did I?
by Vasily Kuznetsov Oct. 23, 2018

Oct. 23, 2018

Hi everyone! Upon running the tests of pytest-console-scripts plugin with pytest 3.9.1 I see 72 deprecation warnings for an API that, as far as I can tell, my plugin doesn't use (see https://github.com/kvas-it/pytest-console-scripts/issues/14 for more details). After replacing the warning in question with an exception in pytest sources I get the full stack trace but it doesn't have any of my code (also documented in the ticket). Could somebody who understands the newly deprecated features take a look at my code (there's not much, the whole extension is just 168 lines of code in one file <https://github.com/kvas-it/pytest-console-scripts/blob/master/pytest_consol…>) and see if there's something I should be doing differently to avoid the warnings. Pointers to the description of which APIs are planned for removal in 4.0 would also work. Cheers, Vasily

2 2

pytest 3.9.2
by Bruno Oliveira Oct. 23, 2018

Oct. 23, 2018

Hi folks, pytest 3.9.2 has just been released to PyPI. This is a bug-fix release, being a drop-in replacement. To upgrade:: pip install --upgrade pytest The full changelog is available at https://docs.pytest.org/en/latest/changelog.html. Thanks to all who contributed to this release, among them: * Ankit Goel * Anthony Sottile * Bruno Oliveira * Ronny Pfannschmidt * Vincent Barbaresi * ykantor Happy testing, The pytest Development Team

1 0

pytest 3.9.x series Released
by RonnyPfannschmidt Oct. 16, 2018

Oct. 16, 2018

Hi everyone, due to a release automation bug i introduced, the first officially published release of the 3.9.x series is 3.9.1 now that its out we finally have a tmp_path fixture among other great improvements. Happy testing! -- Ronny pytest-3.9.1 ======================================= pytest 3.9.1 has just been released to PyPI. This is a bug-fix release, being a drop-in replacement. To upgrade:: pip install --upgrade pytest The full changelog is available at https://docs.pytest.org/en/latest/changelog.html. Thanks to all who contributed to this release, among them: * Bruno Oliveira * Ronny Pfannschmidt * Thomas Hisch Happy testing, The pytest Development Team pytest-3.9.0 ======================================= The pytest team is proud to announce the 3.9.0 release! pytest is a mature Python testing tool with more than a 2000 tests against itself, passing on many different interpreters and platforms. This release contains a number of bugs fixes and improvements, so users are encouraged to take a look at the CHANGELOG: https://docs.pytest.org/en/latest/changelog.html For complete documentation, please visit: https://docs.pytest.org/en/latest/ As usual, you can upgrade from pypi via: pip install -U pytest Thanks to all who contributed to this release, among them: * Andrea Cimatoribus * Ankit Goel * Anthony Sottile * Ben Eyal * Bruno Oliveira * Daniel Hahler * Jeffrey Rackauckas * Jose Carlos Menezes * Kyle Altendorf * Niklas JQ * Palash Chatterjee * Ronny Pfannschmidt * Thomas Hess * Thomas Hisch * Tomer Keren * Victor Maryama Happy testing, The Pytest Development Team

1 0

pytest-steps 1.0.0 is out
by Sylvain MARIE Oct. 16, 2018

Oct. 16, 2018

Dear pytest community pytest-steps 1.0.0 is out! The major change is that it now supports a new “generator” style where test functions can use the `yield` statement to indicate a distinct test step. It makes it relatively transparent and easy to decompose a test into steps, and possibly change your mind later or reorganize the steps. It only relies on fixtures and parameters so as to be as pytest-friendly as possible. The legacy explicit style is still supported of course. I thought that you might be interested: https://github.com/smarie/python-pytest-steps Kind regards -- Sylvain

1 0

Improving pytest internal errors and messages
by Bruno Oliveira Oct. 4, 2018

Oct. 4, 2018

Hi everyone, Often some errors in pytest show a long traceback with the pytest internals, which is noisy and distracting. For example, if a user makes a typo when declaring the scope of a fixture, we get an error like this: ``` ============================================= ERRORS ============================================== _____________________________ ERROR collecting test-scope-mismatch.py _____________________________ src\_pytest\fixtures.py:699: in scope2index return scopes.index(scope) E ValueError: 'modu' is not in list During handling of the above exception, another exception occurred: src\_pytest\runner.py:201: in __init__ self.result = func() src\_pytest\runner.py:265: in <lambda> call = CallInfo(lambda: list(collector.collect()), "collect") src\_pytest\python.py:475: in collect self.session._fixturemanager.parsefactories(self) src\_pytest\fixtures.py:1321: in parsefactories ids=marker.ids, src\_pytest\fixtures.py:837: in __init__ scope or "function", descr="fixture {}".format(func.__name__), where=baseid src\_pytest\fixtures.py:703: in scope2index descr, "from {} ".format(where) if where else "", scope E ValueError: fixture fix from test-scope-mismatch.py has an unsupported scope value 'modu' !!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 1 errors during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!! ===================================== 1 error in 0.16 seconds ===================================== ``` I've opened a WIP PR (https://github.com/pytest-dev/pytest/pull/4077) to deal with this which uses a specific exception type to raise errors in pytest that are "user errors", suppressing the full traceback unless `-vvv` is used. ``` ============================================= ERRORS ============================================== _____________________________ ERROR collecting test-scope-mismatch.py _____________________________ fixture fix from test-scope-mismatch.py has an unsupported scope value 'modu' !!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 1 errors during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!! ===================================== 1 error in 0.07 seconds ===================================== ``` This new exception type (I've used UsageError on my PR just for proof of concept) should be part of the public API so plugins can also use it. I'm writing to the ML because it would be beneficial to get feedback from a larger audience about what the *name* of the exception should be. UserError? InternalError? Feedback on the overall approach (exception usage, verbosity handling, etc) is also very welcome! (On the PR there is a list of issues that could use the new mechanism to provide better messages) Cheers, Bruno.

3 4

trying to figure out which hook(s) I need to use...
by Dj Gilcrease Oct. 3, 2018

Oct. 3, 2018

I am attempting to build a plugin which given 1. discover-able tests; test_foos.py::test_a, test_users.py::test_b, test_foos.py::test_c, test_foos.py::test_d 2. a "plan" structure like https://pastebin.com/dBwjshRm will produce output like https://pastebin.com/hJ7LGPBY I have the logic in pytest_collection_modifyitems to do so, but the parameterize mark does not work there since pytest_collection_modifyitems is run after pytest_generate_tests and pytest_generate_tests does not seem to have access to enough context to allow me to know which set of parameters I need to use. The main complication is that tests can appear multiple times in a plan/scenario, be parameterized with differing values, and must maintain execution order defined in the plan.

1 0

pytest 3.8.2 released!
by Anthony Sottile Oct. 2, 2018

Oct. 2, 2018

pytest 3.8.2 has just been released to PyPI. This is a bug-fix release, being a drop-in replacement. To upgrade:: pip install --upgrade pytest The full changelog is available at https://docs.pytest.org/en/latest/changelog.html. Thanks to all who contributed to this release, among them: * Ankit Goel * Anthony Sottile * Bruno Oliveira * Daniel Hahler * Denis Otkidach * Harry Percival * Jeffrey Rackauckas * Jose Carlos Menezes * Ronny Pfannschmidt * Zac-HD * iwanb Happy testing, The pytest Development Team

1 0