rneovim.git/test/busted/outputHandlers, branch newfeatures Neovim fork with Rahm's personal hacks. fix(test runner): handle nil in no-colors output handler #15679 2021-09-16T18:42:00+00:00 Justin M. Keyes justinkz@gmail.com 2021-09-16T18:42:00+00:00 9d5d72c388b404c7e9e7aedd521bb5abe46c9436 Problem: 13748512f6d6 #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. 
Problem:
13748512f6d6 #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.
 docs: third-party licenses, TEST_COLORS, system() #15665 2021-09-14T17:20:33+00:00 Justin M. Keyes justinkz@gmail.com 2021-09-14T17:20:33+00:00 b63b4777ec80069e42326778023db30bd8217f1a 






fix(build): add an env var to re-enable the colors
2021-09-11T21:20:00+00:00

Björn Linse
bjorn.linse@gmail.com

2021-09-11T20:52:41+00:00

5087347e3b3c8846e2019f36b674d788139c7f69












test(busted): disable colors in test-runner output #15610
2021-09-09T16:18:43+00:00

Justin M. Keyes
justinkz@gmail.com

2021-09-09T16:18:43+00:00

13748512f6d6dfb5895c2233d2e07480e00eb753

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...




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...






test/LSP: assert contents of log file
2020-02-17T06:09:28+00:00

Justin M. Keyes
justinkz@gmail.com

2020-02-17T03:02:09+00:00

6e13b9d26134210f0963341bd77c64a4437f37ec












tests: busted: nvim handler: display durations always (#11075)
2019-09-25T00:20:32+00:00

Daniel Hahler
git@thequod.de

2019-09-25T00:20:32+00:00

db6b4b677d611a2891a5b6d686e485aea08a8f81

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).




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).






Fix test/busted/outputHandlers/TAP.lua (#10881)
2019-08-29T20:11:51+00:00

Daniel Hahler
git@thequod.de

2019-08-29T20:11:51+00:00

00d46f63286461eec4d7b2d7cae15fbe0d9cabdb

Extending the original TAP handler was not working as expected.
This adds a new function for displaying the log.

Ref: https://github.com/neovim/neovim/pull/10876




Extending the original TAP handler was not working as expected.
This adds a new function for displaying the log.

Ref: https://github.com/neovim/neovim/pull/10876






tests: move "busted" dir to "test" (#10518)
2019-07-16T20:02:50+00:00

Daniel Hahler
git@thequod.de

2019-07-16T20:02:50+00:00

34c6e5beaf1f02b5291fcdc27e320cda72720ad4

* 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




* 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