Mailman 3 December 2019 - pytest-dev

New plugin: pytest-unordered
by Ivan Dec. 24, 2019

Dec. 24, 2019

Greetings! After participation in this discussion on GitHub https://github.com/pytest-dev/pytest/issues/5548 I have created a new plugin: https://github.com/utapyngo/pytest-unordered I need some feedback on it as it is my first pytest plugin. We have been using in in a commercial project for a month. I also think that it is better to move it to pytest-dev to share some of the maintenance responsibility if such a small plugin is worth it. Ivan

1 0

returning from my break and choosing my role
by RonnyPfannschmidt Dec. 23, 2019

Dec. 23, 2019

Hi everyone, in the last few weeks i have ramped up my involvement with pytest after taking a longer break. In my time of reflection i came to a few conclusions i want to share. The need for my break after all in part originated from caring too much about things that don't actually matter to me as a person. Its not sensible for me to stay on top of all the things and it destroys the time frames i actually have for contributing the things that i want to bring in. Back around 2005 when i i started with pytest, it was very simple and i could actually easily fix issues with pytest in a testsuite for that little while it took Holger to actually pick it up and fix it better in pytest itself. Over the following years, as my involvement with pytest grew and expanded, the feature-set pf pytest, as well as our technical debt from trying hard not to break things for users grew. Between 2016 i had taken it very hardly on myself that we cannot nicely iterate on this technical debt which turned pytest from something where i can easily fix a bug that affects my testsuite from my testsuite into something where that is not the case anymore. I had also taken it in on myself that some issues (like marker transfer between sibling classes) would affect some users gravely. And a fix was incredible hard to come by back then. My self-introspection while taking the pause has lead me to a few questions and my personal answers. What do i want to be responsible for ? What do i want to feel responsible for ? What do i want out of my Involvement ? Its important to answer those with a good base-level of the "good selfishness" which is there to preserve our own selves in the world and to assert our own position. In future i will no longer be on top of all the issues in some sense (in fact, ignoring issues that don't spark my interest has left me with time to do more about things that i care about, both pytest and other things). In future i will work on guiding and developing pytest into a direction where users will actually be able to fix bugs that affect them in a own testsuite until we fix it right. In future i will work on community building - i want the community of pytest to grow, i want the number of pytest core developers to grow and i want the number of active umbrella plugins to grow. For that a vibrant, including and encouraging community setup is needed (plus community builder is a great self development goal, i have so many rough edges at community communication that i want to smooth/reshape). And while aiming for that a primary goal of mine will be joy * joy of developing and bringing things forward * joy of interacting and helping people/myself to grow * joy of being in control of what i do for who and when i do it. I'm choosing a future that i will enjoy and and i invite everyone to join me in the journey of choosing a personal future abundant with the positive. Whats coming next is that i'm going to keep slowly organizing myself around the changes i want to bring forward and slowly bringing them into reality in small sustainable steps. Part of that already manifests in my proposals/changes to the development processes and the Node Structures. The rest will reveal itself as i refine my own processes and start to communicate better/more structured. Regards, Ronny

2 1

pytest 4.6.8 released!
by Anthony Sottile Dec. 20, 2019

Dec. 20, 2019

pytest 4.6.8 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: * Anthony Sottile * Bruno Oliveira * Ryan Mast Happy testing, The pytest Development Team

1 0

pytest 5.3.2
by Bruno Oliveira Dec. 14, 2019

Dec. 14, 2019

pytest 5.3.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: * Anthony Sottile * Bruno Oliveira * Claudio Madotto * Daniel Hahler * Jared Vasquez * Michael Rose * Ran Benita * Ronny Pfannschmidt * Zac Hatfield-Dodds Happy testing, The pytest Development Team

1 0

[proposal] installing the psf-chronegrapher into pytest-dev
by RonnyPfannschmidt Dec. 7, 2019

Dec. 7, 2019

Hi everyone, in https://github.com/pytest-dev/pytest/issues/6080 it was noted that https://github.com/apps/psf-chronographer ensures towncrier notes are in prs, i would like to propose enabling it for all of pytest-dev Ronny

3 5

pytest 4.6.7 released
by Bruno Oliveira Dec. 6, 2019

Dec. 6, 2019

pytest 4.6.7 has just been released to PyPI. This is a bug-fix release for the 4.6.X series, the last pytest series that supports Python 2.7 and 3.4, 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 * Daniel Hahler Happy testing, The pytest Development Team

1 0

-k EXPRESSION: How to allow for case-insensitive matching
by Christoph Buelter Dec. 5, 2019

Dec. 5, 2019

Greetings, the -k EXPRESSION matching behaviour of the pytest CLI, which deselects tests based on the given expression, is case-sensitive. The relevant code of the KeywordMapping is just a few lines: https://github.com/pytest-dev/pytest/blob/master/src/_pytest/mark/legacy.py… That means using pytest -k statistics will match def test_statistics(): ... but it will not match: class TestStatistics: ... I would have to do some shenanigans like pytest -k "atistics" or pytest -k "statistics or Statistics" to match both tests, just because one happens to be a class and the other a function. Personally, I find that a bit strict and limiting, considering it tests for string inclusion which is rather lax in comparison. It would be very convenient to be able to match both with a single expression, e.g. to filter tests by topics. I know I can mark tests or add extra_keyword_matches, but that isn't very convenient. I also acknowledge that the default behaviour can't be changed as it would break existing code. I have not found a way to customize this with the existing CLI/hooks. Do you think there is any possibility to add some CLI/config option like "--case-insensitive-expression" to make this configurable, or do you consider this to belong to userland? A hook to allow changing the behaviour from a pytest plugin would be totally sufficient as well. I'd be willing to provide a PR if there is any interest. My current workaround is to monkeypatch the behaviour at runtime, which does the job, but is kind of magical and will break when pytests internal structure changes in the future: https://gist.github.com/cb109/de0cf181aaaadf13539be9854c53586c Thanks for pytest by the way :) Cheers, Christoph

7 12