pytest-tap
pytest-tap copied to clipboard
Test Anything Protocol (TAP) reporting plugin for pytest
Not sure if this is by design or a bug.. but it would be helpful to output the errors somehow if the test errors out during the test collection phase....
As of tap version 13 YAML blocks are supported. Tappy allows for reading these YAML blocks but it would be great if the pytest tap plugin could write the YAML...
Currently, if a test marked in Pytest as [xfail](https://docs.pytest.org/en/stable/how-to/skipping.html#xfail-mark-test-functions-as-expected-to-fail) (expected to fail) actually fails, it increments the count of not-ok tests. My proposal consists in adding a new option `--tap-xfail-ok`...
It probably doesn’t matter for the majority of consumers, but perhaps switching to [TAP spec v14](https://testanything.org/tap-version-14-specification.html) might make sense? It seems to be more detailed and better defined, too.
updates: - [github.com/astral-sh/ruff-pre-commit: v0.11.2 → v0.14.10](https://github.com/astral-sh/ruff-pre-commit/compare/v0.11.2...v0.14.10)
To accept your contribution, please complete the checklist below. * [ ] Is your name/identity in the AUTHORS file alphabetically? * [ ] Did you write a test to verify...
Hi there, I am currently packaging pytest-tap for Debian and using the tarball from https://pypi.org/project/pytest-tap/#files for that. It would be nice if you could include the file `conftest.py` in there....
pytest tries to highlight failed assertions but fails. I guess the reason is pytest-tap unregisters "terminalreporter" plugin. test_sample.py: ```python def test_fail(): a = [1] b = {2} assert a ==...