nvsinner-testing-and-qa

Run regression tests for Neovim configuration changes by executing the Plenary Busted test harness, which validates real-Neovim behavior through defined specs and async verification patterns. The workflow includes running the full test suite, interpreting failures, and triaging broken specs.

Writing regression-safe specs for Neovim modules involves following defined spec-writing conventions, establishing test seams, implementing async verification patterns, and documenting the specific behaviors each existing test protects against future configuration changes.

Neovim test suite failures after core module modifications occur when existing specs detect behavior regressions. Diagnose failures by running the Plenary Busted harness, checking real-Neovim behavior expectations, and verifying async patterns and notification capture mechanisms remain intact.

Acceptance evidence required before merging Neovim configuration changes includes passing syntax checks, successful headless boots, full Plenary Busted test runs, and documented empirically discovered behavior validating that no existing regression specs were broken.

Plenary Busted supports async verification patterns and notification capture for Neovim testing, enabling real-Neovim behavior validation. The testing workflow defines these mechanisms to ensure configuration changes are properly validated against actual runtime behavior.

Update existing Neovim test specs after configuration changes when the modified behavior alters what a current regression test protects. Use the testing workflow to identify affected specs, write updated regression definitions, and validate completion evidence before considering the task complete.