neovim/test/functional/legacy/options_spec.lua

-- Test if ":options" throws any exception. The options window seems to mess
-- other tests, so restart nvim in the teardown hook

local helpers = require('test.functional.helpers')
local command, clear = helpers.command, helpers.clear

describe('options', function()
  setup(clear)

  it('is working', function()
    command('options')
  end)
end)
test: Simplify/fix options_spec.lua The options_spec.lua suite has one purpose: Check if the :options commands will throw any exception(:options is implemented by $VIMRUNTIME/optwin.vim). For this it is best to use the `vim_command` API function since it will automatically catch exceptions and forward them via msgpack-rpc. Also, the option window seems to affect other tests, so call `restart` in the teardown hook. 2014-11-04 11:48:18 -07:00			`-- Test if ":options" throws any exception. The options window seems to mess`
			`-- other tests, so restart nvim in the teardown hook`
legacy tests: migrate test_options 2014-10-22 15:34:54 -07:00
			`local helpers = require('test.functional.helpers')`
test: Improve test environment setup and error handling/reporting During test setup, we used to call a vimscript function(BeforeEachTest) that attempted to restore Nvim to it's initial state as much as possible in order to provide a clean environment for running new tests. This approach has proven to be unreliable, as some tests leave state that can affect other tests, eventually causing failures that are difficult to debug. This commit changes the 'clear' function so it will restart Nvim every time it is called, which is a slower, but more reliable solution that will simplify spotting bugs in the future. Some other improvements/fixes were also performed: - Whenever an error is detected in a handler passed to "run()", the event loop will be stopped and the error will be propagated to the main thread. - Errors and the "cleanup()" function will always send a quit command to the current Nvim instance. This should prevent memory starvation when running tests under valgrind(where each Nvim instance can consume a lot of memory). - Fixed a wrong assertion in server_requests_spec.lua. Previously the failure was undetected in a notification handler. - Fixed some tests to expect fully clean registers. The deleted cleanup function used to put an empty string in every register, but that resulted in a extra line being added. 2014-11-06 19:54:49 -07:00			`local command, clear = helpers.command, helpers.clear`
legacy tests: migrate test_options 2014-10-22 15:34:54 -07:00
			`describe('options', function()`
			`setup(clear)`

			`it('is working', function()`
test: Simplify/fix options_spec.lua The options_spec.lua suite has one purpose: Check if the :options commands will throw any exception(:options is implemented by $VIMRUNTIME/optwin.vim). For this it is best to use the `vim_command` API function since it will automatically catch exceptions and forward them via msgpack-rpc. Also, the option window seems to affect other tests, so call `restart` in the teardown hook. 2014-11-04 11:48:18 -07:00			`command('options')`
legacy tests: migrate test_options 2014-10-22 15:34:54 -07:00			`end)`
			`end)`