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.
*	refactor(test): inject after_each differently	Lewis Russell	2024-04-10
\|
*	test: improve test conventions	dundargoc	2024-04-08
\| \| \| \|	Work on https://github.com/neovim/neovim/issues/27004.
*	test: rename (meths, funcs) -> (api, fn)	Lewis Russell	2024-01-12
\|
*	test: typing for helpers.meths	Lewis Russell	2024-01-12
\|
*	refactor: format test/*	Justin M. Keyes	2024-01-03
\|
*	fix(:let): fix error when applying operator to boolean option (#24030)	zeertzjq	2023-06-15
\|
*	test(let_spec): increase expect_exit() timeout	zeertzjq	2022-08-05
\| \| \|	Test ":unlet self-referencing node in a List graph #6070" feeds many characters into typeahead, so a timeout of only 100 milliseconds sometimes fails. Change that timeout to 1000 milliseconds.
*	test: deal with RPC call causing Nvim to exit later	zeertzjq	2022-07-19
\|
*	fix(ex_cmds): correct flags for :const (#19387)	zeertzjq	2022-07-16
\|
*	refactor(tests): introduce testprg()	Justin M. Keyes	2022-06-25
\| \| \| \| \| \|	Also: - Add a describe('shell :!') section to system_spec. - Make the test for #16271 work on systems without powershell.
*	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
*	refactor(tests): remove redir_exec #15718	Justin M. Keyes	2021-09-19
\| \| \| \| \| \| \| \| \| \| \|	Problem - `redir_exec` is obsolete, but it keeps getting used in new tests because people copy existing tests. - Disadvantages of `redir_exec`: - Captures extra junk before the actual error/message that we _want_ to test. - Does not fail on error, unlike e.g. `command()`. Solution - Use new functions like `nvim_exec` and `pcall_err`.
*	test: reorg #15698	Justin M. Keyes	2021-09-17
	Problem: Subdirectories like "visual", "insert", "normal" encourage people to separate related tests for no good reason. Typically the _mode_ is not the relevant topic of a test (and when it is, _then_ create an appropriate describe() or it()). Solution: - Delete the various `test/functional/<mode>/` subdirectories, move their tests to more meaningful topics. - Rename `…/normal/` to `…/editor/`. - Move or merge `…/visual/` and `…/insert/` tests into here where appropriate. - Rename `…/eval/` to `…/vimscript/`. - Move `…/viml/` into here also. test(reorg): insert/* => editor/mode_insert_spec.lua * test(reorg): cmdline/* => editor/mode_cmdline_spec.lua * test(reorg): eval core tests => eval_spec.lua