Mailman 3 April 2021 - pytest-dev

Transfer of pyfakefs to pytest-dev?
by mrbean-bremen Sept. 30, 2022

Sept. 30, 2022

After the successful transfer of pytest-order (thank you for that smooth experience!), I have been thinking about the transfer of another library - pyfakefs - where I am a contributor. I have been discussing this with the package maintainer, John McGehee, who is also in favor for this, and decided to first ask here if that is feasible. pyfakefs (https://github.com/jmcgeheeiv/pyfakefs) is a library that mocks the file system. It has originally been developed by Mike Bland at Google, later transferred to GitHub (after the shutdown of Google Code in 2011), where John McGehee has forked it, added direct support for unittest and doctest, and has maintained it since then (with my help since a few years ago). Later a contributor added support for pytest via the fs fixture, with more support for pytest following eventually. Today the fs fixture is probably the main means to access pyfakefs, judging by the issues and the dependent repositories. So, while pyfakefs is not a pure pytest plugin, and it doesn't follow the naming convention pytest-xx, we thought that it would be a good idea to transfer it to pytest-dev, with the following goals: - ensure continued maintenance - increase compatibility with pytest and pytest-plugins - improve visibility of the package, especially for pytest developers - ideally, benefit from the larger community to get more code reviews and issue reports For reference see also https://github.com/jmcgeheeiv/pyfakefs/issues/590 What do you think? Thanks! -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

5 8

proposal: plugin metadata
by Eduardo Schettino April 24, 2021

April 24, 2021

Hi, I would like to propose a mechanism to improve the plugin list page. https://docs.pytest.org/en/latest/reference/plugin_list.html Currently there are over 800 plugins and relying on someone manually curated them is not really feasible. So the idea is to allow plugin authors to set some metadata that could in turn be used to generate a more informative plugins page. More specifically it should: Clearly state to which version of pytest the plugin is compatible. Currently it shows the last release date and minimum required version. But it is not really clear if the latest version of pytest is supported/tested. Define one or more categories. Going through a list of 800+ plugins is a lot of work. Could define categories like: - framework-integration: i.e. pytest-airflow, pytest-django - output/report: i.e. pytest-clarity - coverage - ordering - etc.. In future could also add some more stuff, like download stats, github stars, etc. So the first step would be to define a schema and agree on a format (JSON?). What do you guys think? As a reference see how grafana does it: https://grafana.com/docs/grafana/latest/developers/plugins/metadata/ Regards

2 1

How can I suppress cleanups when a test fails
by Eliot, Christopher April 17, 2021

April 17, 2021

My test suit generates some intermediate files and other resources which typically would be deleted upon termination of the test. However, if there is a failure, I would like to leave them in place to help in diagnosing the failure. Is there a clean way to do this? I'm already using a fixture to do cleanup, so I'm prepared to use some aspect of the fixture if that's appropriate. Thanks, Topher Eliot

3 5

pytest 6.2.3
by Ran Benita April 3, 2021

April 3, 2021

pytest 6.2.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/stable/changelog.html. Thanks to all of the contributors to this release: * Bruno Oliveira * Ran Benita Happy testing, The pytest Development Team

1 0