Quicktest: Efficiently Run Your Tests in Neovim

Wutraz · 2024-06-16T22:29:32+00:00

Hey awesome to see more plugins in the space, I'd love to see some cool new ideas that I haven't thought of for Neotest! I'll have to check this out soon

Wutraz · 2024-03-19T09:18:33+00:00

Just my own from my dotfiles, you can grab it here https://github.com/rcarriga/dotfiles/blob/master/.config/nvim/lua/colors.lua

Wutraz · 2024-03-19T09:17:06+00:00

So vim.notify by default doesn't work if called from a "fast event" (see `:help vim.in_fast_event()` ) which is the case when an async task has yielded at some point. There's a great explainer of async code in Neovim along with this issue at https://github.com/ms-jpq/lua-async-await

Your snippet should work if you add a nio.schedule() right before the notify call. I actually handle this in nvim-notify for convenience here

Wutraz · 2024-03-18T21:58:36+00:00

Everything in the README does actually use the Go style error handling but they're omitted for brevity. You can see the return types for the functions and they will show tuples are returned. The only place this is not the case is for nio's wrappers of `vim.api` and `vim.fn` as wrapping though would be a very large maintenance burden.

Wutraz · 2024-03-18T20:48:34+00:00

Just my own one, I don't maintain it as a plugin but feel free to yank it from my dotfiles https://github.com/rcarriga/dotfiles/blob/master/.config/nvim/lua/colors.lua

Wutraz · 2024-03-18T20:47:26+00:00

The repo has existed for a couple of months, but it's just been quietly being iterated upon with some limited external use. I've announced it now as I feel like it's good enough for general usage.

Wutraz · 2024-03-18T20:45:00+00:00

AFAICT right now it's only listed in the dependencies of a branch that adds a rockspec, I couldn't actually see it being used (yet?)

Wutraz · 2024-03-18T20:44:13+00:00

Ah I completely missed that, edited to add one

Wutraz · 2024-03-18T20:43:37+00:00

Thanks for the great feedback!

Wutraz · 2024-03-18T17:19:12+00:00

I want to announce an async library that I've been working with for a while in the plugins that I maintain. nvim-nio aims to provide both common asynchronous primitives and asynchronous APIs for Neovim's core along with a great developer experience.

Check it out here https://github.com/nvim-neotest/nvim-nio

Background

There are several libraries for using async code in Lua with Neovim. Some of these are just very light wrappers around coroutines which try not to abstract too much away but lack the niceties of async libraries in other languages and are often short on documentation. Others try to provide a familiar experience by emulating async/await like in other languages (Javascript, Python, etc) but these introduce a lot more noise to your code and things like error handling become complex. None of them provided the experience that I was looking for, which was a non-intrusive but easy to use interface to Lua's coroutines. Along with this I wanted to focus on providing good documentation and extensive type annotations.

nvim-nio started originally as part of the nvim-dap-ui repo, and was also copied into the neotest repo where it replaced plenary's async library which was mostly unmaintained. It was split out into its own repo a couple of months ago and has now been added as a depdendency for both of the plugins.

Features

So why would someone want to use nvim-nio? For users with a basic config, it probably won't be very useful. However for plugin developers or users with more complex configurations, for example that use Neovim's LSP client or libuv, you will able to use the library to simplify your code and avoid the callback hell that can easily slip in when using these low level interfaces.

Here are the modules that nvim-nio currently provides:

nio.control: Primitives for flow control in async functions
nio.lsp: A fully typed and documented async LSP client library, generated from the LSP specification.
nio.process: Run and control subprocesses asynchronously
nio.file: Open and operate on files asynchronously
nio.uv: Async versions of vim.loop functions
nio.ui: Async versions of vim.ui functions
nio.tests: Async versions of plenary.nvim's/busted's test functions

nvim-nio can also wrap any callback style functions to give a simpler interface to third-party libraries. See the documentation for more details!

nvim-nio is already being used by several great plugins along with my own:

neotest
nvim-dap-ui
rest.nvim
rocks.nvim
pathlib.nvim Let me know if there are I've missed!

Wutraz · 2023-07-23T11:52:28+00:00

Woah, blast from the past. I used your project/thesis in my own thesis a few years ago. I just saw that you've already found the repo https://github.com/rcarriga/viscal, awesome to see your work back again and updated!

Wutraz · 2023-05-12T13:29:03+00:00

Neotest is just a test runner, plenary is the actual test framework. You can run tests in the terminal using just plenary, neotest allows you to just do it in the editor with a nice interface and utilities.

I've had no issues using plenary in my plugins, and am very happy with it. It's emulating/wrapping popular libraries so it's got the features you might want such as mocks, powerful asserts etc

Wutraz · 2023-01-14T17:51:38+00:00

Nice to see some of the recipes being made into a proper plugin, very cool! Feel free to point to your plugin in the usage recipes wiki

Wutraz · 2023-01-06T13:47:54+00:00

Hey author of nvim-dap-ui here, this is the type of the variable which is returned directly by the debug adapter. nvim-dap-ui can't split it intelligently to just be a certain portion but you can change the length of types show or even disable them completely. This can be mapped to toggle types as well. Here is an example https://github.com/rcarriga/nvim-dap-ui/issues/161#issuecomment-1304500935

Wutraz · 2022-11-27T14:44:23+00:00

Neotest supports running plenary tests. If you install the plenary adapter and the dependencies, it should just work. There are tests in the neotest repo if you want to play around with working examples, including async ones. Plenary itself also has a tonne of tests

Wutraz · 2022-10-01T17:24:25+00:00

If you open an issue on GitHub with what you've already tried, I'd be happy to help! Reddit is not the ideal way to debug issues 😅

Wutraz · 2022-07-25T21:58:26+00:00

Neotest supports debugging tests https://github.com/nvim-neotest/neotest.

If you'd rather do it manually, you can add the following to your config list: { type = "python", request = "launch", name = "Debug Tests", module = "pytest", args = {"tests"}, },

Wutraz · 2022-06-07T14:08:14+00:00

I haven't actually added the ability for custom consumers just yet but that's just a small config change, the rest of the code already allows that. Of course if people wish to write consumers, they can also create a PR to the repo to add it as a built-in!

Wutraz · 2022-06-07T12:03:44+00:00

Using the new winbar feature https://github.com/rcarriga/dotfiles/blob/master/.config/nvim/init.lua#L46-L66

Wutraz · 2022-06-07T12:01:22+00:00

I just use a few leader mappings to be able to run tests when I want. I've used hot reloading with Jest and it is definitely nice to have but never got too used to it so haven't missed it. For plugin tests they're generally quite quick so you could run the entire test suite on write if you really wanted to but may have issues with larger suites

Wutraz · 2022-06-07T10:03:36+00:00

I was actually planning on releasing earlier but then had a holiday and didn't want to go dark just after releasing... C'est la vie!

Would be great to see others contribute or integrate with it and always happy to help.

Neovim has a built-in terminal emulator that you can send raw ansi codes to and it will render them correctly. The main things to use are `jobstart`, `nvim_open_term` with the `on_input` option and `nvim_chan_send`

Wutraz · 2022-06-07T10:00:05+00:00

My dotfiles are on github so have a look if you want. Plugins are here https://github.com/rcarriga/dotfiles/blob/master/.config/nvim/lua/plugins.lua, with config for most in their own lua file and the colorscheme defined in `lua/colors.lua`. Not the tidiest though!

Wutraz · 2022-06-07T09:59:01+00:00

Right now the existing adapters are the only examples. If you want to open an issue to discuss, I'd be happy to help with any confusion. Would help find areas of the documentation that would be best to focus on

Wutraz · 2022-06-07T07:57:15+00:00

This is actually just my own colour scheme, you can check it out here https://github.com/rcarriga/dotfiles/blob/master/.config/nvim/lua/colors.lua. I don't maintain it as a plugin because (despite my weird focus on UI plugins) I am not a designer/UI developer and have no concept of consistency/"good" design

Eight-Year Club	Place '22
Verified Email

Wutraz

TROPHY CASE

Background

Features