aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/api/buffer.c
diff options
context:
space:
mode:
authorThiago de Arruda <tpadilha84@gmail.com>2014-05-23 15:49:51 -0300
committerThiago de Arruda <tpadilha84@gmail.com>2014-05-23 16:06:59 -0300
commit6c96e42e2c18bd6ae685b5a41c69b03954aa0375 (patch)
treed25a81cd37939466e5b9c8b33b3566f9aefbdf49 /src/nvim/api/buffer.c
parentf03a7672e18fe57b1e4de17abf2a193f8b343562 (diff)
downloadrneovim-6c96e42e2c18bd6ae685b5a41c69b03954aa0375.tar.gz
rneovim-6c96e42e2c18bd6ae685b5a41c69b03954aa0375.tar.bz2
rneovim-6c96e42e2c18bd6ae685b5a41c69b03954aa0375.zip
API: Test: Setup basic test infrastructure
- Add a 'expect' utility script that can run simple API tests using clients developed for any platform. - Extend travis build matrix to run API tests using the python client and valgrind. This script can be used to write API tests without having to manage nvim's lifetime: - It starts a single nvim instance listening on a known socket - Invokes the test runner, which should connect to NEOVIM_LISTEN_ADDRESS - The nvim instance started by the script provides a `BeforeEachTest` function, which should be called before each test to reset nvim to a clean state. - It takes care of shutting down nvim once the tests are finished. As explained [here](https://github.com/neovim/neovim/pull/737#issuecomment-43941520), it's not possible to fully reset nvim to it's initial state, but the `BeforeEachTest` function should be enough for most test cases. Tests requiring a fully clean nvim instance should take care of starting/stopping nvim.
Diffstat (limited to 'src/nvim/api/buffer.c')
0 files changed, 0 insertions, 0 deletions