neovim/test/functional/preload.lua

-- Modules loaded here will NOT be cleared and reloaded by Busted.
-- Busted started doing this to help provide more isolation.  See issue #62
-- for more information about this.
local t = require('test.testutil')
require('test.functional.ui.screen')

if t.is_os('win') then
  local ffi = require('ffi')
  ffi.cdef [[
  typedef int errno_t;
  errno_t _set_fmode(int mode);
  ]]
  ffi.C._set_fmode(0x8000)
end
feat(logging): include test-id in log messages Problem: 1. Log messages (especially in CI) are hard to correlate with tests. 2. Since b353a5c05f02 #11886, dumplog() prints the logs next to test failures. This is noisy and gets in the way of the test results. Solution: 1. Associate an incrementing id with each test and include it in log messages. - FUTURE: add v:name so Nvim instances can be formally "named"? 2. Mention "child" in log messages if the current Nvim is a child (based on the presence of $NVIM). BEFORE: DBG … 12345 UI: event DBG … 12345 log_server_msg:722: RPC ->ch 1: … DBG … 12345 UI: flush DBG … 12345 inbuf_poll:444: blocking... events_enabled=1 events_pending=0 DBG … 23454 UI: stop INF … 23454 os_exit:594: Nvim exit: 0 AFTER: DBG … T57 UI: event DBG … T57 log_server_msg:722: RPC ->ch 1: … DBG … T57 UI: flush DBG … T57 inbuf_poll:444: blocking... events_enabled=1 events_pending=0 DBG … T57/child UI: stop INF … T57/child os_exit:594: Nvim exit: 0 2022-05-23 21:44:15 -07:00			`-- Modules loaded here will NOT be cleared and reloaded by Busted.`
tests: prevent busted from reloading the ffi module and others It turns out that Busted started cleaning the environment in 2.0rc5 as a result of Olivine-Labs/busted#62. This, in turn, caused the ffi module to be reloaded for each spec file, and LuaJIT doesn't appreciate it. The net effect is an assertion error in LuaJIT. By using the --helper feature of Busted, we can pre-load some modules ahead of Busted and prevent it from reloading them--making LuaJIT happy again. 2015-03-01 12:49:48 -07:00			`-- Busted started doing this to help provide more isolation. See issue #62`
			`-- for more information about this.`
test: improve test conventions Specifically, functions that are run in the context of the test runner are put in module `test/testutil.lua` while the functions that are run in the context of the test session are put in `test/functional/testnvim.lua`. Closes https://github.com/neovim/neovim/issues/27004. 2024-04-20 08:44:13 -07:00			`local t = require('test.testutil')`
test: remove unused variable (#21552) 2022-12-28 16:20:42 -07:00			`require('test.functional.ui.screen')`
test/functional/preload.lua: _set_fmode for Windows 2019-09-11 04:47:23 -07:00
test: improve test conventions Specifically, functions that are run in the context of the test runner are put in module `test/testutil.lua` while the functions that are run in the context of the test session are put in `test/functional/testnvim.lua`. Closes https://github.com/neovim/neovim/issues/27004. 2024-04-20 08:44:13 -07:00			`if t.is_os('win') then`
test/functional/preload.lua: _set_fmode for Windows 2019-09-11 04:47:23 -07:00			`local ffi = require('ffi')`
			`ffi.cdef [[`
			`typedef int errno_t;`
			`errno_t _set_fmode(int mode);`
			`]]`
			`ffi.C._set_fmode(0x8000)`
			`end`