gtest-vim VS vim-dispatch

The plugin depends on cmake4vim (a plugin for CMake integration with Vim/Neovim), this allowed to have deeper integration of gtest-vim for CMake projects (you can just switch between CMake targets in order to run different tests).

Tis is good for the compilation to make it async( otherwise it blocks) https://github.com/tpope/vim-dispatch it wraps around the built in make/makeprg feature. Would recommend that you dont do it with large builds/outputs.

vim-dispatch by the legend Tim Pope. send the task to the background, keep using editor. once the task is finished, it output to qflist buffer

The other answer here covers everything you need, but if you want a plugin-based solution you might be interested in vim-dispatch which runs command line tools asynchronously, and offers the option to run the command in the background instead with :Dispatch!.

You should check :h compiler :h make and :h 'errorformat'. You could also check vim dispatch, a plugin that enhances this features

Also plugin supports asynchronous execution (using terminal, jobs or vim-dispatch).

Do note that :make is blocking, and you need to wait until it finishes before it sends you back to the editor. If you want it to be asynchronouns, you can install vim-dispatch + vim-dispatch-neovim for Neovim support in vim-dispatch.

if you want something to work out of the box, is async and is already configured per language, check out TPope's dispatch

For long-running programs, like compiling, or running full test suites, or running terraform on a decently sized infrastructure project, I may run them with :Make (courtesy of tpope/vim-dispatch) so I can keep working on the project while the external program is running. If I'm in an environment without vim plugins, I may spawn a new tmux pane/window. As a last resort, I will ctrl-z/fg if I don't have tmux on the remote system (e.g. dev containers).