Replies: 1 comment 1 reply
-
As far as I'm aware there is no unified API or something like that yet. When I started out with nvim-dap and nvim-jdtls I briefly looked at https://build-server-protocol.github.io/ as it would provide the functionality to discover build targets and to run them and is piggybacking onto LSP & DAP, but unfortunately outside of the scala world it afaik hasn't really seen any adaption (yet). If it did, I think it would be nice to have a unifying test-discovery plugin for neovim as well (that would utilize nvim-dap and the built-in lsp client) Other than that there is https://github.com/rcarriga/vim-ultest as a testing framework (with nvim-dap support) All the extensions so far provide dedicated "test nearest method" functions:
They just search for the nearest test (often via tree-sitter) and then call
|
Beta Was this translation helpful? Give feedback.
-
Recently in Metals we added support for test discovery to support the VS Code Testing API. Under the hood tests are still actually ran via DAP, and I was curious to play around with something like this to easily allow a user to run individuals tests or suites with a more finer granularity then the "test target" or "test file" that Metals currently has. However I was curious if something like this has ever been explored or if someone has already played around with this? Basically something similar to the Packer window that opens up and you'd be able to trigger tests and see them update using ext marks.
Do you know if this has been looked into at all?
Beta Was this translation helpful? Give feedback.
All reactions