Closed hendrikbursian closed 1 month ago
Hey @hendrikbursian and thanks for the super detailed bug report! ⭐
Ah, I think I see the problem here. Right now, each test's output is being filtered so only the exactly one matching test will show its output for each test run. But it does make sense to show all subtest output too, of a given test. Especially when you think how some of sub-tests will be difficult to detect, like this integer iteration one. Just like you experienced, the output of the subtests are not seen anywhere!
I am on vacation currently, and I just whipped up a really quick and dirty fix for this, which I'm not sure is going to be stable enough on its own... but perhaps. I just want to make sure you won't start seeing other unrelated test output for a given test, before merging it in.
Please give it a go if you wish by using neotest-golang with branch = "fix-for-range-test"
in your lazy.nvim config.
Wow, what a turnaround time!
I saw it's already merged into main - its working for me.
Thank you and enjoy your vacation!
Did you check docs and existing issues?
Neovim version (nvim -v)
v0.10.0
Operating system/version
Ubuntu 22.04
Describe the bug
Hi, thanks for the plugin!
I just noticed that the logging of errors for subtests doesn't show up for me as they did a few weeks ago. The commit that is causing the problem for me is e4d8020a9df2883f0cf417d37aaf79a0759a4473. I am using the standard config (without the coverage generation).
Please let me know if you need more information or if its something I overlooked.
Kind regards
Hendrik
Testfile
Output on commit e4d8020a
Output on commit c9e6fe5d (previous commit)
Steps To Reproduce
t.Run()
(see bug report)Expected Behavior
When I run a failing subtest I want to be able to see the log of the failed subtest. For example:
Your Lua setup