A Neovim plugin that displays test coverage data in the sign column and summary reports for multiple programming languages.
nvim-coverage is a Neovim plugin that displays test coverage information directly in the editor's sign column and provides summary reports. It helps developers visualize which parts of their code are covered by tests and identify gaps in test coverage without leaving the editor.
Neovim users who write tests in supported languages (like Python, JavaScript, Go, Rust) and want to monitor coverage interactively during development.
It offers a lightweight, editor-integrated solution with broad language support and customizable visuals, avoiding the need to switch to external tools for coverage insights.
Displays test coverage data in the sign column
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports over a dozen languages including Python, JavaScript, Go, and Rust, with the ability to handle any language generating LCOV files, as detailed in the README's language list.
Displays coverage markers directly in Neovim's sign column for real-time feedback, with screenshot examples showing covered and uncovered lines highlighted.
Offers extensive options to customize highlights, signs, thresholds, and language settings, as shown in the configuration example with commands and highlight groups.
Allows adding support for new languages via simple Lua modules, documented with required methods, making it adaptable to niche or custom toolchains.
Branch coverage is only partially supported for four languages (JavaScript/TypeScript, Python, Dart, Julia), with Dart and Julia marked as untested in the README, and many major languages like Go and Rust lack support entirely.
Does not execute tests or generate reports itself; it relies on external test suites and other plugins, which can fragment the workflow and add setup overhead.
For PHP with cobertura reports, it requires an optional luarock dependency (lua-xmlreader), adding an extra installation step and potential compatibility issues.