Replies: 2 comments 4 replies
-
It's not a bug, more just poor intended behaviour. There wasn't much reasoning to adding child errors to the parent result, we could remove that functionality from neotest and leave the error messages completely up to adapters. I think it makes more sense that way than assuming that errors should be collected by parents. I'll have to double check for any side effects of that change but you can test yourself by just removing this line https://github.com/nvim-neotest/neotest/blob/master/lua/neotest/client/runner.lua#L219 |
Beta Was this translation helpful? Give feedback.
-
https://github.com/nvim-neotest/neotest/blob/master/lua/neotest/client/runner.lua#L219 is an empty line. So which line should I remove? I thought the whole |
Beta Was this translation helpful? Give feedback.
-
Hi,
while adding errors to the neotest-go adapter (nvim-neotest/neotest-go#14), I stumbled upon following feature of neotest:
The adapter returns the following result, which looks fine IMHO:
But neotest testrunner adds here
neotest/lua/neotest/client/runner.lua
Line 31 in 8f4e4e3
the error of the subtest to the main test:
This leads to the error of line 19 been added 3 times to the diagnostics:
There must be some reason why neotest is doing this - but I don't understand this. Is there something in the original adapter result wrong? Or is this a bug in neotest?
Thanks and regards
Jens
Beta Was this translation helpful? Give feedback.
All reactions