pytest-metadata
pytest-metadata copied to clipboard
pytest-dev
Plugin for accessing test session metadata
updates: - https://github.com/psf/black → https://github.com/psf/black-pre-commit-mirror - [github.com/psf/black-pre-commit-mirror: 24.1.1 → 25.12.0](https://github.com/psf/black-pre-commit-mirror/compare/24.1.1...25.12.0) - [github.com/pre-commit/pre-commit-hooks: v4.5.0 → v6.0.0](https://github.com/pre-commit/pre-commit-hooks/compare/v4.5.0...v6.0.0) - [github.com/PyCQA/flake8: 7.0.0 → 7.3.0](https://github.com/PyCQA/flake8/compare/7.0.0...7.3.0)
![pre-commit-ci[bot] avatar](https://avatars.githubusercontent.com/in/68672?v=4 "pre-commit-ci[bot] avatar"){kind=avatar}
After some more fiddling, the incompatibility might come from pytest-metadata and pytest... it seems pytest-metadata doesn't support pytest >= 8.0.0 yet, and that makes the report generation fail for some...
I am unable to see my environment info on my html report, even my html and metadata plugins are fully upgraded and running plugins: anyio-3.7.1, html-3.2.0, metadata-3.0.0, xdist-3.3.1
Hello, I wish to add my own section that includes test configurations so I can separate information about test env. and test config. Is it possible to add it already...
Is it possible next time on release new version make the github release to have entry on https://github.com/pytest-dev/pytest-metadata/issues entries? 🤔 I'm asking because only on make gh release is spread...
It seems the `Release note` link is pointing to the wrong address. 
[Requirements](https://requires.io/github/pytest-dev/pytest-metadata/requirements/?branch=master) in the readme file redirecting to a domain that's up for sale. 
Looks like requires.io is dead, and project isn't using Travis anymore. So may as well remove badges Resolves #91
Hi, Would it be possible to introduce typing to the plugin's code? I've just integrated this plugin into one of my test suites, and the typing would help me realise...
There's a matter of making sure to include py.typed in a built package