rneovim.git - Neovim fork with Rahm's personal hacks.

	Commit message (Collapse)	Author	Age
*	test: improve test conventions	dundargoc	2024-04-23
\| \| \| \| \| \| \| \| \|	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.
*	test: remove unnecessary nil argument to testutil (#28270)	zeertzjq	2024-04-11
\|
*	test: fix off-by-one test IDs in logs (#28269)	zeertzjq	2024-04-11
\| \| \| \| \| \| \|	Run the global before_each() before all other before_each(), so that clear() uses the test ID of the current test, not the previous one. Don't skip generating test IDs for skipped tests, as that'll make a skipped test have the same test ID as the previous one.
*	test: improve test conventions	dundargoc	2024-04-08
\| \| \| \|	Work on https://github.com/neovim/neovim/issues/27004.
*	refactor: format test/*	Justin M. Keyes	2024-01-03
\|
*	test: remove unused variable (#21552)	Raphael	2022-12-29
\|
*	fix(tests): only get the color map once, even for multiple test files	bfredl	2022-11-27
\| \| \| \| \| \| \| \| \|	Problem: test/functional/ui/screen.lua would be reloaded for each *_spec.lua file, which causes an extra nvim session to be started to get the color map each time. solution: Mark screen.lua as a preloaded file, but defer the loading of the color map to the first time Screen object is initialised.
*	test: simplify platform detection (#21020)	dundargoc	2022-11-22
\| \| \| \| \|	Extend the capabilities of is_os to detect more platforms such as freebsd and openbsd. Also remove `iswin()` helper function as it can be replaced by `is_os("win")`.
*	feat(logging): include test-id in log messages	Justin M. Keyes	2022-06-15
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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
*	test/functional/preload.lua: _set_fmode for Windows	Daniel Hahler	2019-09-25
\|
*	functests: Check logs in lua code	ZyX	2016-06-10
\| \| \| \| \| \|	It is otherwise impossible to determine which test failed sanitizer/valgrind check. test/functional/helpers.lua module return was changed so that tests which do not provide after_each function to get new check will automatically fail.
*	Remove dependency on ffi module	Thiago de Arruda	2016-03-07
\|
*	tests: prevent busted from reloading the ffi module and others	John Szakmeister	2015-03-01
	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.