rneovim.git/test/busted/outputHandlers, branch tmp

test(report): formatting, drop dumplog()

2022-06-16T02:23:10+00:00

Don't need to dumplog() on each failed test because we now have test-ids
that associate log messages with tests.

feat(logging): include test-id in log messages

2022-06-16T02:23:10+00:00

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: don't print NVIMLOG on success

2022-03-29T20:50:39+00:00

fix(test runner): handle nil in no-colors output handler #15679

2021-09-16T18:42:00+00:00

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

fix(build): add an env var to re-enable the colors

2021-09-11T21:20:00+00:00

test(busted): disable colors in test-runner output #15610

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

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[33m[ SKIPPED ][0m[0m [36m

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

tests: busted: nvim handler: display durations always (#11075)

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

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

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