Introducing: continuous-testing.nvim

This page summarizes the projects mentioned and recommended in the original post on /r/neovim

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • nvim-treesitter

    Nvim Treesitter configurations and abstraction layer

  • Add vim-signs based on test results. (with the help of nvim-treesitter)

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • nvim-notify

    A fancy, configurable, notification manager for NeoVim

  • Get notified when the tests are finished. (great with nvim-notify)

  • trouble.nvim

    🚦 A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing.

  • Great feedback, thanks! I’ll certainly have a look into using the LSP to reduce the amount of tests to run. For me, the notifications are a handy feature since our ruby code runs in a docker container. It takes quite some time to attach to the container and run the test file. (This was actually one of the motivations for writing this plugin) However, you can disable notifications and rely completely on the diagnostics. With another plugin like trouble.nvim, you could see the updates in a separate window. Only downside to this, it will be cluttered with other LSP diagnostics. I chose this approach since I am not a fan of creating just another status window, maybe I’ll have to revisit this opinion.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts