| Age | Commit message (Collapse) | Author |
|---|
|
Problem: Extra newline in messages after a verbose shell message.
Solution: Output the newline with msg_putchar_attr(). (closes #11233)
Make it possible to filter a screendump before comparing it.
|
|
Problem: 'fillchars' cannot have window-local values.
Solution: Make 'fillchars' global-local. (closes #5206)
|
|
Problem: Screendump test may fail when using valgrind.
Solution: Wait longer for the first screendump.
|
|
Problem: CTRL-A does not work properly with the cmdline popup menu.
Solution: Fix issues with CTRL-A. Add more tests for the cmdline popup
menu. Remove TermWait() before VeriryScreenDump(). Refactor the
cmdline popup code. (Yegappan Lakshmanan, closes #9735)
|
|
Problem: Setting local instead of global flag.
Solution: Prepend "g:" to "test_is_flaky".
|
|
Problem: Not all tests using a terminal are in the list of flaky tests.
Solution: Introduce the test_is_flaky flag.
|
|
Problem: Tests contain typos.
Solution: Correct the typos. (Dominique Pelle)
|
|
Problem: Shared functions for testing are disorganised.
Solution: Group finctions in script files. (Ozaki Kiichi, closes #4573)
|
|
Problem: The command displayed to show a failing screenshot does not include
the "testdir" directory.
Solution: Prefix the directory name so that it can be copy-pasted.
|
|
Problem: No cmdline redraw when tabpages have different 'cmdheight'.
Solution: redraw the command line when 'cmdheight' changes when switching
tabpages. (closes #4321)
|
|
Problem: Writing coverage info in a separate dir is not needed.
Solution: Revert the changes to use a separate directory.
|
|
Problem: Not all screen update code of the terminal window is executed in
tests.
Solution: Redraw before taking a screenshot.
|
|
Problem: Incorrect coverage information; typo in color name.
Solution: Fix the typo. Set environment variables to have a nested Vim
write the coverage info in another directory.
|
|
Problem: When making a new screendump test have to create the file.
Solution: Continue creating the failed screendump, so it can be moved once
it is correct.
|
|
Problem: When a screendump test fails, moving the file is a hassle.
Solution: Instead of appending ".failed" to the file name, keep the same
file name but put the screendump in the "failed" directory.
Then the file name only needs to be typed once when moving a
screendump.
|
|
Problem: Cannot see in CI why a screenshot test failed.
Solution: Add info about the failure.
|
|
Problem: GUI may wait too long before dealing with messages. Returning
early may cause a mapping to time out.
Solution: Use the waiting loop from Unix also for the GUI.
(closes #3817, closes #3824)
|
|
Problem: Parsing of 'diffopt' is slightly wrong.
Solution: Fix the parsing and add a test. (Jason Franklin, Christian
Brabandt)
|
|
Problem: No clue what test failed when using a screendump twice.
Solution: Add an extra argument to VerifyScreenDump().
|
|
Problem: Keys to stop Vim in terminal are wrong. (Marius Gedminas)
Solution: Move ":" to before CTRL-U.
|
|
Problem: Stoping Vim running in a terminal may not work.
Solution: Instead of sending <Esc> send CTRL-O.
|
|
Problem: Difficult to make a plugin that feeds a line to a job.
Solution: Add the nitial code for the "prompt" buftype.
|
|
Problem: Duplicate term options after renaming.
Solution: Remove the old names 'termkey', 'termsize' and 'terminalscroll'.
|
|
Problem: In tests, when WaitFor() fails it doesn't say why. (James McCoy)
Solution: Add WaitForAssert(), which produces an assert error when it fails.
|
|
Problem: No test for using the 'termsize' option.
Solution: Add a test.
|
|
Problem: Various tests are still a bit flaky.
Solution: Increase the default wait time to five seconds.
|
|
Problem: Terminal API test is a bit flaky.
Solution: Wait longer for Vim to stop.
|
|
Problem: Terminal window tests are flaky.
Solution: Increase the waiting time for Vim to start.
|
|
Problem: Screen dump is made too soon.
Solution: Wait until the ruler is displayed. (Ozaki Kiichi, closes #2755)
|
|
Problem: Terminal API tests still fail.
Solution: Explicitly set 'title' in the terminal job. (Ozaki Kiichi,
closes #2750)
|
|
Problem: Running Vim in terminal fails with two windows.
Solution: Pass the number of rows to RunVimInTerminal().
|
|
Problem: Job in terminal can't communicate with Vim.
Solution: Add the terminal API.
|
|
Problem: Popup test fails depending on environment variable.
Solution: Reset $COLORFGBG when running Vim in a terminal. (closes #2693)
|
|
Problem: Testing with Vim running in terminal is a bit flaky.
Solution: Delete any .swp file so that later tests don't fail.
|
|
Problem: Popup menu positioning fails with longer string.
Solution: Only align with right side of window when width is less than
'pumwidth' (closes #2661)
|
|
Problem: No test for the popup menu positioning.
Solution: Add a screendump test for the popup menu.
|
|
Problem: C syntax test still fails when using gvim.
Solution: Clear Normal cterm highlighting instead of setting it.
|
|
Problem: C syntax test fails when using gvim
Solution: Force running in a terminal. Check that 'background' is correct
even when $COLORFGBG is set.
|
|
Problem: No test using a screen dump yet.
Solution: Add a test for C syntax highlighting. Add helper functions.
|
