Access of pytest-cov report from within another plugin

[Zaloog]

Hello,
I am currently developing a pytest plugin, and want to access the coverage report generated by pytest-cov.
The report is written in the pytest_terminal_summary-hook src

I understand I can get a reference to the plugin with

cov_plugin = config.pluginmanager.get_plugin("pytest_cov")

but that just gives access to the module, not the cov_report from the CovPlugin class.
Is there an obvious way I am missing to get the desired attribute?

[nicoddemus]

Looking at https://github.com/pytest-dev/pytest-cov/blob/9463242e3a7bc18a56b8f18c01b4dfb50087e5ed/src/pytest_cov/plugin.py#L193, seems you can get it by using get_plugin("_cov"), but that looks like is not intended for external access.

Also consider asking directly in the pytest-cov repository.

[Zaloog]

Could've sweared, I tried the "_cov" alone part...
But ye that works. getplugin("_cov").cov_report.getvalue() gives the string output.
Thanks :)

[The-Compiler]

Depending on what exactly your goal is, you might just want to get the report from coverage itself in a machine-readable format instead. You can also get the text report directly from coverage as well.

[Zaloog]

Hi @The-Compiler,
also thanks for your Tutorial in Darmstadt, learned some more tweaks about pytest there :)

I am currently working on a plugin (ayu), which utilizes also uv to be able to be run as an independent tool (uvx ayu) and therefore can install itself, "on the fly" when running your tests, e.g. with uv run --with ayu pytest.
Ayu itself opens a tui interface and starts a websocket, and the plugin part sends test collections/reports/outcomes/... to the application.
One can also mark tests and run for example just the marked tests.
I got the coverage report string already and turned it into a dict to work with.
Just connected it the tui, currently the tool looks like this:

[Zaloog]

Screen.Recording.2025-05-13.at.19.06.33.mov

[The-Compiler]

That looks amazing 🤩! But I'd really recommend getting the data via the coverage Python API to begin with, rather than hacking around the plugin's private code and parsing things from a string.