nvim-neotest/neotest

An extensible framework for interacting with tests within NeoVim.

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 22nd, 2026
Created on January 2nd, 2022
Open Issues & Pull Requests: 104 (+0)
GitHub issues: Enabled
Number of forks: 186
Total Stargazers: 3,114 (+0)
Total Subscribers: 11 (+0)

Repository Insights (GitGenius)

Median issue/PR response: N/A
Mean response time: 18.4 days
90th percentile: 42.3 days
Tracked items: 83

How this project is maintained

100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 56% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 48
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 596 days
Stale 30+ days: 46
Stale 90+ days: 36

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (2)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Neotest is a framework for interacting with tests within NeoVim.

The tool addresses the need to run, debug, and inspect test results without leaving the editor. It works by providing a plugin architecture where language-specific adapters parse test files using Treesitter, execute tests through various runners, and display results directly in NeoVim windows. The framework handles test discovery, execution strategies, and result collection through a unified interface.

Neotest suits developers who want integrated test interaction within their NeoVim workflow and need support for multiple test runners and languages. The project requires installing an adapter for your specific test runner alongside the core framework and its dependency on nvim-nio. The tool is early-stage software, so adopters should expect ongoing development and potential API changes.

The project shows active maintenance with regular updates to core functionality and adapter support. Development includes ongoing refinement of the framework's architecture and expansion of test runner coverage through community-contributed adapters. The maintainers actively address issues and incorporate feedback on the framework's design and usability.