Problem: Cmdexpand.c insufficiently tested.
Solution: Add more tests. (Yegappan Lakshmanan, closesvim/vim#5789)
24ebd83e03
Map Q to gQ before every test since a test uses :mapclear.
Problem: Try-catch test fails.
Solution: Don't call win_enter(), only call enterering_window().
bdf931c25b
v8.2.1781 caused Test_reload_in_try_catch() from v8.2.0004 to fail in Vim, but
it has not been ported yet.
Problem: Not all tests using a terminal are in the list of flaky tests.
Solution: Introduce the test_is_flaky flag.
3cdcb090a6
Cherry-pick g:test_is_flaky from patch v8.2.0557.
Ensure that test_is_flaky variable is set from the global scope..
N/A patches for version.c:
vim-patch:8.2.2647: terminal test sometimes hangs
Problem: Terminal test sometimes hangs.
Solution: Wait for the shell to display a prompt.
f4a2ed0714
vim-patch:8.2.2648: terminal resize test sometimes hangs
Problem: Terminal resize test sometimes hangs.
Solution: Wait for the shell to display a prompt and other output.
c54f347d63
fixup! vim-patch:8.2.0400: not all tests using a terminal are in the list of flaky tests
Problem: No ATTENTION prompt for :vimgrep first match file.
Solution: When there is an existing swap file do not keep the dummy buffer.
(closesvim/vim#6649)
8ce4b7ed85
Problem: MS-Windows: test log contains escape sequences.
Solution: Do not use t_md and t_me but ANSI escape sequences. (Ken Takata,
closesvim/vim#6559)
45df2a01a7
Problem: In some environments a few tests are expected to fail.
Solution: Add $TEST_MAY_FAIL to list tests that should not cause make to
fail.
ce436de5a9
Problem: Tests get stuck when running into an existing swapfile.
Solution: Set v:swapchoice to "q" and report an error. (Daniel Hahler,
closesvim/vim#4644)
b073da8929
Problem: Time reported for a test measured wrong.
Solution: Move the computation to the end of RunTheTest(). (Ozaki Kiichi,
closesvim/vim#4520)
640d4f0c97
Problem: Cannot easily select one test function to execute.
Solution: Support the $TEST_FILTER environment variable. (Ozaki Kiichi,
closesvim/vim#2695)
a7f6c3cf07
Problem: No statistics displayed after running tests.
Solution: Summarize the test results. (Christian Brabandt, closesvim/vim#4391)
Also make it possible to report a skipped file.
9c0cec65f8
Removes our custom no-inits from `$(RUN_VIMTEST)`, since we have
`$(NO_INITS)` now also.
Problem: Test listed as flaky should no longer be flaky.
Solution: Remove Test_popup_and_window_resize from the list of flaky tests.
(Daniel Hahler, closevim/vim#4807)
9570aacdb8
Fails often on CI (OSX), e.g.:
```
1 FAILED:
Found errors in Test_cursorhold_insert():
function RunTheTest[37]..Test_cursorhold_insert line 9: Expected 1 but got 0
```
> Compiler: clang Xcode: xcode10.1 C
The test could be adjusted to re-try the timer a few times, but I do not
think it's really worth it currently, and that the test should be marked
as flaky instead.
Problem: If a test function exists Vim this may go unnoticed.
Solution: Check for a test funtion quitting Vim. Fix tests that did exit
Vim.
8903676d3d
Restore test_assert.vim to run Test_zz_quit_detected().
Problem: Flaky test sometimes fails in different ways.
Solution: When the second run gives a different error, try running the test
again, up to five times.
f77af0e613
Problem: When test_edit fails 'insertmode' may not be reset and the next
test may get stuck. (James McCoy)
Solution: Always reset 'insertmode' after executing a test. Avoid that an
InsertCharPre autocommand or a 'complete' function can change the
state. (closesvim/vim#3768)
8ad16da729
