nvim-test

Run Neovim plugin tests with plenary.nvim in headless mode.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/khwerhahn/okuban.nvim --skill nvim-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nvim-test
Source: https://github.com/khwerhahn/okuban.nvim/tree/main/.claude/skills/nvim-test
Command: npx skills add https://github.com/khwerhahn/okuban.nvim --skill nvim-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a repeatable way to run Neovim plugin tests in headless mode, removing manual test invocation and ensuring consistent test execution for okuban.nvim development.

Core Features & Use Cases

  • Headless test execution: Run the full test suite without opening the editor UI.
  • Targeted file runs: Execute a single test file for rapid iteration during development.
  • CI and local parity: Use identical invocations locally and in continuous integration to reproduce failures reliably.
  • Test conventions: Expects tests in the tests/ directory, follows busted-style _spec.lua naming, and uses tests/minimal_init.lua to isolate plugin loading.

Quick Start

Start Neovim in headless mode and run Plenary's test runner against the tests directory using the minimal_init.lua to execute all plugin tests.

Frequently Asked Questions about nvim-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Neovim plugin tests in headless mode?

Run Neovim plugin tests in headless mode by executing Plenary's test runner against your tests directory. This Skill automates the invocation using a minimal_init.lua file to isolate plugin loading without opening the editor UI.

Can I run a single busted spec file with plenary.nvim during development?

Yes, you can run a single busted-style _spec.lua file for rapid iteration. This Skill supports targeted file runs alongside full test suite execution to speed up local Neovim plugin development.

What do I need to set up Neovim headless testing with plenary?

You need Neovim with plenary.nvim installed, a tests directory containing busted-style _spec.lua files, and a minimal_init.lua file for isolated plugin loading to execute headless test runs successfully.

Why use a minimal_init.lua for Neovim plugin test execution?

Using a minimal_init.lua isolates plugin loading during headless test execution. It ensures consistent test environments by preventing unrelated Neovim configurations from interfering with plenary.nvim test runs.

Can I use the same Neovim test commands in local development and CI?

Yes, this Skill provides identical headless test invocations for both local development and continuous integration. Using the same plenary.nvim commands ensures reliable reproduction of test failures across environments.

What are the limitations of running Neovim tests headlessly with plenary?

Headless testing with plenary.nvim requires strict adherence to busted-style _spec.lua naming conventions and a properly configured minimal_init.lua. Tests relying on interactive UI elements or manual user input will not execute correctly in headless mode.