Closed mrcjkb closed 1 year ago
There are two things that need to be fixed:
-p
option if no matches are found.function :: [TestTree]
as a neotest namespace.Do you think tree-sitter could be able to walk up the tree of nodes and detect the testGroup
that's just up ahead of the function that defines the list of tests?
Do you think tree-sitter could be able to walk up the tree of nodes and detect the
testGroup
that's just up ahead of the function that defines the list of tests?
I would have to add some queries to tasty-positions.scm for that. It should be possible, but IIRC, I tried that once and it broke a bunch of other stuff, so I gave up on it. I will look into it again later.
For now, #104 implements a hotfix by adding -p
arguments for each top-level testCase
when running all tests in a file.
@all-contributors please add @Kleidukos for bug
@mrcjkb
I've put up a pull request to add @Kleidukos! :tada:
Closing this as fixed by #104 and opened #107 for the more complicated query enhancement.
Neovim version (nvim -v)
nightly
Operating system/version
NixOS 23.05
How to reproduce the issue
Place cursor on the function's type signature (test file:
and run neotest
Expected behaviour
neotest runs all tests within the
[TestTree]
and outputs the results as virtual textActual behaviour
neotest tries to run all tests and outputs an error message. This is because
neotest-haskell
can't find any test groups and passes-p $0~
with no paths to match.A minimal Neovim config used to reproduce this issue.