Open duguyue100 opened 1 year ago
Also, here is my setup
require("neotest").setup({
diagnostic = {
enabled = true
},
adapters = {
require("neotest-vim-test")({ allow_file_types = { "python" } }),
},
highlights = {
passed = "NeotestPassed",
running = "NeotestRunning",
failed = "NeotestFailed",
skipped = "NeotestSkipped",
test = "NeotestTest",
namespace = "NeotestNamespace",
focused = "NeotestFocused",
file = "NeotestFile",
dir = "NeotestDir",
border = "NeotestBorder",
indent = "NeotestIndent",
expand_marker = "NeotestExpandMarker",
adapter_name = "NeotestAdapterName",
select_win = "NeotestWinSelect",
marked = "NeotestMarked",
},
icons = {
expanded = "",
collapsed = "",
passed = "✅",
running = "✨",
failed = "❌",
unknown = "❔",
},
})
I can't reproduce so I'm not sure what the issue is. Does using neotest-python have any effect?
NeoVim Version Output of
nvim --version
Describe the bug A clear and concise description of what the bug is.
As shown in the following image, when running
NetstRunNearest
, after it's finished, the checkmark is actually not at the line of the test function, but the one above. At first, I thought this is a misalignment, but later I found out that this actually runs the test above this one.To Reproduce
This is all I have for configuring neotest
Expected behavior A clear and concise description of what you expected to happen.
The checkmark at the test function line and actually run the correct test.