-
Currently there's no way to detect which one to use, in my case, it's hard coded to pytest -- it would be nice to have a way to detect the runner type depending on the file/root etc
-
I don't currently think this is a feature, at least it's not auto updating for me in Python.
Currently I have another terminal window open which auto runs my unit tests when any python file changes…
-
My full Neotest config:
```lua
require('neotest').setup({
discovery = { enabled = false },
adapters = {
require('neotest-plenary'),
require('neotest-rust'),
require('neotest-j…
-
I'm not quite sure if this is reproducible in other machines.
## Reproduction
Install .NET 7 SDK
```
dotnet new xunit -n IssueRepro
```
Run `IssueRepro.UnitTest1.Test1`
## Expected be…
-
Hi! This project looks super cool and it looks like it's brand new! Super excited to try it out. I've run into an issue when running it, so I thought I'd post here :)
```
❯ rustc --version
rustc …
-
`require('neotest').summary.open()` is really cool.
It would be even cooler if pressing `` on a test name would jump your cursor to that test in the main buffer.
-
Is there a way to do this? I couldn't figure out a way reading `:h neotest.Config.summary.mappings`.
-
fe5fbe4e344fd1e822eee50d907ebd7aab031d54 breaks test discovery for projects installed with `pip install -e .`. I did not test yet if it also breaks without `-e`. If you want I can set up a repo with a…
tbung updated
2 years ago
-
I'm not sure if this is a neotest or neotest-python issue, so I decided to open it here. I'm using [fzf](https://github.com/junegunn/fzf) and [fzf.vim](https://github.com/junegunn/fzf.vim) with a `Git…
-
When I set `output.open_on_run = true`, I expected Neotest to open the output window after running a test, even if the test passes, but no window opened. Is this expected behavior?
This is my Neote…