Mathew Attlee

Regarding your last point do you mean like this which vim-test already does? ```vim let test#strategy = { \ 'nearest': 'neovim', \ 'file': 'dispatch', \ 'suite': 'basic', \} ```

@janko I know understand why this isn't working, it's because `test#base#nearest_test_in_line` goes through line by line which means that multi-line matching for test nearest isn't currently possible. Any suggestions on...

What if test nearest match started at a single line and then kept expanding in range in both directions till a match was found? For example I run it at...

Thank for you very much for this information, it would make a fantastic addition to the wiki

The same issue happens across all runners. I have got around the issue myself by opening each sub-project in a different tab and change the working in each tab using...

Thank you for this PR, could you include the changes from #543 and that will make the tests in this PR pass

That would be great to add Typescript support. Could you please link to some documentation for the runner you would like to add and I'll advise as best as I...

Perhaps the simplest solution might be a strategy

To clarify are your tests written in JavaScript or TypeScript?

I see your point. Given the way the plugin works, you would have to duplicate the existing JavaScript runners to make TypeScript versions. I don't think this can be avoided...