PlenaryBustedDirectory hangs when run from existing NeoVim instance

Open
#319 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
lua
Domain
testing

Research direction

Start at the PlenaryBustedDirectory command and compare its behavior when invoked from a headless Neovim process versus an existing Neovim instance. Reproduce with test/ifactor_spec.lua and the commands in the report; done means the in-editor run proceeds past the Scheduling popup and completes the test execution.

Written by the indexing model from the issue text.

Description

I can run plenary tests from the command line. For instance, I have a project ifactor with one test file in test/ifactor_spec.lua. This works:

$ cd /path/to/ifactor/root
$ nvim --headless -c "PlenaryBustedDirectory test {minimal=true}"

However, when I try the same thing inside Neovim, I get a popup window that just says "Scheduling: /Users/smackesey/stm/code/lib/vim/ifactor/test/ifactor_spec.lua" and nothing else:

:cd /path/to/ifactor/root
:PlenaryBustedDirectory test {minimal=true}

So the test files are correctly discovered but then something goes awry in the execution.

Dominant language
Lua
Stars
3.5k
Forks
340
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nvim-lua/plenary.nvim

All issues in nvim-lua/plenary.nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.