The pytest team is proud to announce the 6.1.0 release!
This release contains new features, improvements, bug fixes, and breaking changes, so users
are encouraged to take a look at the CHANGELOG carefully:
https://docs.pytest.org/en/stable/changelog.html
For complete documentation, please visit:
https://docs.pytest.org/en/stable/
As usual, you can upgrade from PyPI via:
pip install -U pytest
Thanks to all of the contributors to this release:
* Anthony Sottile
* Bruno Oliveira
* C. Titus Brown
* Drew Devereux
* Faris A Chugthai
* Florian Bruhin
* Hugo van Kemenade
* Hynek Schlawack
* Joseph Lucas
* Kamran Ahmad
* Mattreex
* Maximilian Cosmo Sitter
* Ran Benita
* Rüdiger Busche
* Sam Estep
* Sorin Sbarnea
* Thomas Grainger
* Vipul Kumar
* Yutaro Ikeda
* hp310780
Happy testing,
The pytest Development Team
Dear Admin,
I was working in a project which uses Pytest framework for testing purpose and we were blocked when we encountered a situation were the test cases has to be executed in a user defined manner , so after doing proper research I have developed a plugin which have satisfied our need , so I thought of making this plugin a global one so other developers might use this feature in their work based on the requirement. Please find the code in the following repository and help me making this plugin a common one among the Pytest community , I was all open for any suggestions.
https://github.com/SivaRamSV/Pytest_Test_suite_sequence
Thanks and Regards,
Sivaram SV.
pytest 6.0.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/stable/changelog.html.
Thanks to all of the contributors to this release:
* Bruno Oliveira
* Ran Benita
Happy testing,
The pytest Development Team
About two weeks ago I created the https://github.com/pytest-dev/meta project with the hope of being used for tracking organization wide issues (and avoid having to pollute our main pytest project).
I seen use of "meta" on many github organizations for the same purpose, "stuff" that is unrelated to the code of a specific repository. I hope it will become popular. I do also see other benefits as used of a mailing list sets a higher barrier for people that are not yet fully dedicated (we do all know experienced the "Ahh not another ML!" sensation).
Early today I also added the first ticket, the proposal for adoption of the testinfra plugin, see https://github.com/pytest-dev/meta/issues/1 and comment there.
Cheers,
Sorin
