neotest-ctest adapter

[orjangj]

First of all, I want to thank you for making this plugin. I've been using it for quite some time now and it works like a charm so far.

Anyway, I found this issue #68 and I noticed that neotest was brought up in the discussion.

I have written a neotest adapter for C/C++ using CTest as a test runner. You can find it here: https://github.com/orjangj/neotest-ctest. It currently supports basic test macros from both GoogleTest (TEST, TEST_F) and Catch2 (TEST_CASE, TEST_CASE_METHOD, SCENARIO). I plan to add support parameterized tests (if possible) and add support for more test frameworks as well.

I'm not sure where to take it from here, but I figured you might want to have a look at it and maybe reference it in the README?

Let me know what you think. If not, you can just close this issue :)

[Civitasv]

I think this is very interesting! Currently, we parse all tests using ctest command and no other dependencies, lacking some features. But I'm not familiar with neotest, to my understanding now, I think it's like a middleware which provides unified API to support multiple test framework, right?

[orjangj]

Yes, in short neotest provides a unified API and UI to run tests, while neotest adapters will take care of constructing commands to run tests in addition to parsing test results. One of the things that makes neotest such a great plugin is that you can use it for many different languages/frameworks (provided there is an adapter available) and that you get feedback on passing/failing test in the sign column. Neotest can also display test output (parsed by adapters) in a floating window, show errors through nvim's diagnostics (if supported by the adapter), and more.

neotest-ctest bridges neotest, ctest and a few supported C/C++ test frameworks. neotest-ctest is primarily limited by its ability to parse test cases through treesitter (which determines how neotest knows what tests you want to run). There's bound to be some shortcomings here considering that building treesitter queries can be quite challenging for some of the test case macros (especially parameterized tests). After that, the adapter will simply query ctest for runnable tests and build the appropriate ctest command(s) to run a single test case, all tests in a file or all tests in a directory/workspace depending on how you invoked neotest's API.

neotest-ctest does not manage cmake based projects or compile tests, which is why I've recommended cmake-tools.nvim as a companion plugin in my readme :)

[mjrogozinski]

I was looking for a plugin like this one.
In the project with multiple test binaries, I would like to be able to say "run this test" and only the test binary (CMake target) containing the test would be rebuilt.

Integration of CMake with testing frameworks is needed. Thank you for your work.

[Civitasv]

neotest-ctest does not manage cmake based projects or compile tests, which is why I've recommended cmake-tools.nvim as a companion plugin in my readme :)

I figured you might want to have a look at it and maybe reference it in the README?

@orjangj I would like to reference your work in README. Can you write a guide on how to use your plugin with cmake-tools, I kinda stuck on setting up it, it shows nothing, I already symlink CTestTestfile.cmake.

[orjangj]

Hi @Civitasv. Sorry for the late response.

The plugin only supported system lib include patterns like #include <gtest/gtest.h> as opposed to #include "gtest/gtest.h", but I just updated the master branch with a commit to support both styles now.

Can you try again? Should work without the symlinking as the plugin is able to detect the CTestTestfile.cmake two levels deep.

Example steps:

• Build/compile project and tests with :CMakeBuild command (and recompile as needed when changes are made)
• Run tests within a file via neotest :Neotest run file

I've listed some suggested configs/options for neotest in my README under usage if you're interested in looking at different keybindings.

Let me know if you're still running into issues or need more information.