Closed tfrs1 closed 1 year ago
As in the title, the neotest.summary window is showing incorrect status at at least the file level.
neotest.summary
From what I've been able to gather, this is related to changes in https://github.com/nvim-neotest/neotest-go/pull/39, more specifically because of hard-coding the result status to "failed" on all file nodes. I understand that neotest is supposed to determine the status of the file node from the leaves automatically. I'm tagging you @sergii4 because you are the author.
"failed"
Hi @tfrs1, could you please update. I believe the issue was fixed in #44
You're right. Sorry for the false alarm.
As in the title, the
neotest.summary
window is showing incorrect status at at least the file level.From what I've been able to gather, this is related to changes in https://github.com/nvim-neotest/neotest-go/pull/39, more specifically because of hard-coding the result status to
"failed"
on all file nodes. I understand that neotest is supposed to determine the status of the file node from the leaves automatically. I'm tagging you @sergii4 because you are the author.