To add on what @aktau said: soon we will have much more robust UI tests. The current UI tests are hard to write and based on the ASCII output [2] of the comman

To add on what @aktau said: soon we will have much more robust UI tests. The current UI tests are hard to write and based on the ASCII output [2] of the commands of the test [1]. By using the Neovim API we will be able to rewrite these tests to look more like automated Sellenium based web app tests and make more fine grained assertions. [1] A test: https://github.com/neovim/neovim/blob/39cdb5f214bcb1e4a918f65ccf6c0c56cbbf8f76/src/nvim/testdir/test10.in https://github.com/neovim/neovim/blob/39cdb5f214bcb1e4a918f6... [2] The expected test output spec: https://github.com/neovim/neovim/blob/39cdb5f214bcb1e4a918f65ccf6c0c56cbbf8f76/src/nvim/testdir/test10.ok https://github.com/neovim/neovim/blob/39cdb5f214bcb1e4a918f6...