nvim-coverage
Displays test coverage data in the sign column (by andythigpen)
nvim
My custom NeoVim setup (by echasnovski)
| nvim-coverage | nvim | |
|---|---|---|
| 3 | 5 | |
| 259 | 85 | |
| - | - | |
| 5.9 | 9.5 | |
| 18 days ago | 2 days ago | |
| Lua | Lua | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nvim-coverage
Posts with mentions or reviews of nvim-coverage.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-06-06.
-
(self) Display Jest / Instanbul code coverage in Neovim
there already is https://github.com/andythigpen/nvim-coverage fyi
-
neotest: A modern, powerful testing plugin
I wrote this plugin a few months ago: nvim-coverage
-
Test coverage plugin
I created a plugin that displays test coverage information called nvim-coverage and I thought I'd share here. It currently supports Python, Ruby, and Rust since those are the three languages I've been using the most lately, but it should be easy enough to extend to other languages that can generate coverage reports in JSON.
nvim
Posts with mentions or reviews of nvim.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-09-02.
-
Neovim lua setup. Init.lua, plugin/, after/plugin folders
Hmm... It should be. Here is my setup and I use both 'init.lua' and 'after/ftplugin'. The latter is sourced every time filetype option is set.
-
Usage of 'after/ftplugin' directory for filetype-specific configuration
This is meant as a Friday post to make more people aware of 'after/ftplugin' directory, because I find this approach really more structured than using autocommands. For reference, here is how I do it.
-
neotest: A modern, powerful testing plugin
It is in "closed alpha", so to speak, i.e. in my Neovim configuration [here](https://github.com/echasnovski/nvim/blob/master/lua/mini-dev/test.lua). Yet needs some Lua experience to go through source code, but it will be easier with more examples in the near future. I plan to release it for beta testing in a couple of weeks.
-
'mini.surround' new features: custom surroundings and search method
Sure, here you go.
-
Advice for r and rmarkdown using vim?
Hi, I use Neovim with R and Rmarkdown without Nvim-R for a quite a while now. Here is my config.
What are some alternatives?
When comparing nvim-coverage and nvim you can also consider the following projects:
neotest - An extensible framework for interacting with tests within NeoVim.
nvim-dap-ruby
neotest-rspec - 🧪 Neotest adapter for RSpec. Works in Docker containers too
dotfiles - My dotfiles
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
refactoring.nvim - The Refactoring library based off the Refactoring book by Martin Fowler
languageserver - An implementation of the Language Server Protocol for R
kcov - Code coverage tool for compiled programs, Python and Bash which uses debugging information to collect and report data without special compilation options