7 Commits

Author	SHA1	Message	Date
Justin M. Keyes	9d5d72c388	fix(test runner): handle nil in no-colors output handler #15679 ... Problem: 13748512f6 #15610 The no-colors codepath of the nvim.lua test output handler does not handle nil, leading to weird symptoms if e.g. a test has a syntax error: test/busted/outputHandlers/nvim.lua:105: attempt to concatenate a nil value Solution: Coerce to string in no-colors handler.	2021-09-16 11:42:00 -07:00
Justin M. Keyes	b63b4777ec	docs: third-party licenses, TEST_COLORS, system() #15665	2021-09-14 10:20:33 -07:00
Björn Linse	5087347e3b	fix(build): add an env var to re-enable the colors	2021-09-11 23:20:00 +02:00
Justin M. Keyes	13748512f6	test(busted): disable colors in test-runner output #15610 ... Problem ------- Because test/busted/outputHandlers/nvim.lua doesn't know if it's running in a terminal (no "isatty" equivalent), it outputs color codes in CI logs and local tooling that runs the tests in a pipe: [1m[ SKIPPED ]  This is just noise, hard for humans to read. Solution -------- Disable the color codes. If we later find a clever way to detect a terminal in nvim.lua, we might consider re-enabling colors, but that would still affect the CI build logs...	2021-09-09 09:18:43 -07:00
Justin M. Keyes	6e13b9d261	test/LSP: assert contents of log file	2020-02-16 22:09:28 -08:00
Daniel Hahler	db6b4b677d	tests: busted: nvim handler: display durations always (#11075) ... This shows them also with test failures/errors, where it is useful to see how long the test took (for flaky failures running into timeout).	2019-09-25 02:20:32 +02:00
Daniel Hahler	34c6e5beaf	tests: move "busted" dir to "test" (#10518) ... * tests: move "busted" dir to "test" It is used for outputHandlers only, and clearly belongs to the tests. Use the full module name with the `-o` option to `busted` then for clarity. * luacheck * test/busted/outputHandlers/TAP.lua: use/extend upstream	2019-07-16 22:02:50 +02:00