-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nothing happens when running tests #25
Comments
Hey, sorry. Were you able to solve it? |
Hello @jfpedroza I'm getting related behavior. I'm using Lazyvim too. When I run neotest I got Any suggestions? |
Does it happen only with Elixir? Have you tried another adapter? |
@garaujodev the only solution I've been able to come up with is to set the |
another solution i just found involves setting the typical This is less-than ideal as it's going to mean initializing a neotest adapter I might not ever use. But, at least it doesn't load the entire plugin 🤷 @jfpedroza I can confirm that using |
I recently migrated from packer to lazy and haven't really tried lazy loading. I have my config in As I understand it, if you specify all the adapters in For example, I have in my vim.schedule(function()
require("neotest").setup_project(vim.loop.cwd(), {
adapters = {
require("neotest-elixir")({
mix_task = "test.interactive",
extra_formatters = { "ExUnit.CLIFormatter", "ExUnitNotifier" },
}),
},
})
end) Adapters are not standalone neovim plugins. They are always loaded by a call when you are setting up neotest. |
Closing as stale. |
Hi,
I am using Lazy to load plugins into NVIM and I am getting no feedback when running
lua require("neotest").run.run()
Here is my NVIM config for testing. I had previously installed vim-test, but then saw the developer was moving to a new project, so I installed that instead.
When I attempt to run the tests, it does nothing and I see no running tests. I am running the tests inside a vanilla scaffolded phoenix project.
Should I see a popup on the screen with test results?
The text was updated successfully, but these errors were encountered: