aboutsummaryrefslogtreecommitdiff
path: root/scripts/run-api-tests.exp
Commit message (Collapse)AuthorAge
* remove scripts/run-api-tests.expJustin M. Keyes2018-04-11
| | | | Usage of this script was removed 0c2ec77ae0c0.
* server: Rename address environment variableThiago de Arruda2014-09-13
| | | | | To follow the pattern of using NVIM for technical descriptions, it was renamed to NVIM_LISTEN_ADDRESS
* test: Remove cleanup function definition from run-api-tests.expThiago de Arruda2014-08-28
| | | | This function is now injected automatically when running the python-client tests
* api tests: set 'initpython' in BeforeEachTestThiago de Arruda2014-07-17
| | | | This is required to run some tests of the python client
* build: increase timeout for run-api-tests.expThiago de Arruda2014-06-18
|
* Build: Fix autocmd removal from cleanup functionThiago de Arruda2014-05-28
|
* API: Test: Setup basic test infrastructureThiago de Arruda2014-05-23
- 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.