-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
conjure
Interactive evaluation for Neovim (Clojure, Fennel, Janet, Racket, Hy, MIT Scheme, Guile, Python and more!)
In terms of testing methodology, you can take a look at some of my specs. It boils down to: edit a file in a temp dir, run some mappings/commands, save the file, check its updated content. In your case, evaluating execute("messages") might give you the output of your plugin, but make sure to use echomsg instead of echo, otherwise it won't end up in the messages output.
I don't have personal experience with it myself, so can't say how well it works. I use my own Vimrunner project for all my plugins (and I prefer it -- easier for me to write tests in ruby than in a custom file format), but it's also based on +clientserver so it won't work for your case. Would be happy to talk over a PR, of course :). But if you don't feel like doing work on testing tools, vroom might be a good option.
You might try the "vroom" project: https://github.com/google/vroom. It uses +clientserver by default, which Neovim doesn't support, but it seems like it has a "neovim mode" as well.
I wrote Aniseed so I could write my plugins in a lisp and run them as Lua, I designed a test suite system around this and some helper scripts to open nvim and execute my test suite when required in CI or locally. It's all kinda half copied from Clojure since I love how testing works in Clojure already.
Ohhh some remarkably similar ideas to my Conjure (well, in the sense that they're about evaluating code). Conjure is all about sending code to a running REPL and interactively developing your application as it runs, so slightly different but still the same category.
The only other example I have is an older plugin of mine: vim-enmasse - that's traditional vimscript so it might be a better example for you.