-
I use neotest with python and have noticed that when I run tests the colorcolumn gets moved to the right by one character on rows where the tick/cross is displayed. The line numbers also get messed up…
-
I'm trying to run tests in an NX monorepo, it works with neotest-vim-test but not with this package
-
When I try to run a test pytest cannot find it. Pytest itself does work. I assume this is an error with the test path given to pytest. I am not sure if this should be an issue with neotest or neotest-…
tbung updated
2 years ago
-
Just wondering if there was a way to run the entire project?
I've tried `require('neotest').run.run(vim.fn.getcwd())` as well as `require('neotest').run.run('./...')` but neither worked.
Wondering…
-
I used to lazy load **vim-ultest** using **keys** and by **cmd** packer properties this way:
```lua
use {
"rcarriga/vim-ultest",
opt = true,
run = ":UpdateRemotePlugins",
…
-
Is there a command to run the entire test suite of a project?
-
Anyone work on this Adapter?
-
I've been really enjoying ultest, so I am very excited about neotest. Thanks for building such great software.
Here are a few things I've noticed on latest neotest:
1. `lua require("neotest").ou…
-
My test output has two things: the result of the test, and a stdout message about code coverage.
For some reason, only the code coverage stdout message is making it into the output file I seen in t…
-
Are the examples supposed to work like this?
https://github.com/rcarriga/neotest/blob/6dede28d9a08157ed955b04278cddc4faa9d8708/doc/neotest.txt#L253
They do work like this:
```lua
lua require("ne…