5 Commits

Author	SHA1	Message	Date
dundargoc	052498ed42	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-23 18:17:04 +02:00
Lewis Russell	81fc27124b	refactor(test): inject after_each differently	2024-04-10 15:53:50 +01:00
dundargoc	7035125b2b	test: improve test conventions ... Work on https://github.com/neovim/neovim/issues/27004.	2024-04-08 22:51:00 +02:00
Justin M. Keyes	04f2f864e2	refactor: format test/*	2024-01-03 02:09:29 +01:00
Justin M. Keyes	d8de4eb685	test: reorg #15698 ... 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	2021-09-17 09:16:40 -07:00