aboutsummaryrefslogtreecommitdiff
path: root/test/functional/ui
Commit message (Collapse)AuthorAge
* api/vim: allow guis and tests to retrieve the entire color tableBjörn Linse2015-02-02
|
* test/ui: update documentation for screen testsBjörn Linse2015-02-02
|
* test/ui: enable strict mode by default (and in existing tests)Björn Linse2015-02-02
|
* test/ui: more informative "unexpected highlight" errorsBjörn Linse2015-02-02
|
* Fix the ctrl + left click test.John Szakmeister2015-01-28
| | | | | | | The test was hoping to not find a tags file, but didn't actively guard against it. In my case, I had a tags file present which was causing different output to be generated. To fix this, let's set the tags option to look for an unlikely filename.
* test: Make default screen timeout depend on the VALGRIND env varThiago de Arruda2015-01-23
| | | | | | While running under valgrind, the screen can take significantly longer to update(especially on travis) so a higher timeout can be required. Also reduce the timeout when not running on valgrind.
* test: Fix hanging test suite after failuresThiago de Arruda2015-01-23
| | | | | | | | | | | | | | | | When a test that fails leaves nvim in a 'Press Enter...' state, the whole suite will hang because the `qa!` command executed before the next test won't be processed until '<enter>' is sent. Now the lua client can send a signal with when `Session:exit()` is called, so the `qa!` request is no longer necessary. Also: - Set noswapfile at startup to prevent tests from leaving .s* swap files(should also improve test environment determinism) - Use `assert(false, msg) instead of `error(msg)` to report screen assertion failures.
* tests/ui: strict modeBjörn Linse2015-01-23
|
* tests/ui: snapshot utilBjörn Linse2015-01-23
|
* test: Fix screen.lua eol_clear method.Thiago de Arruda2015-01-22
|
* test: Add more functional test to cover new codeThiago de Arruda2015-01-15
| | | | | | | | | - emulate gui_running and terminal colors - scrolling/clearing regions - mouse wheel scrolling - setting icon/title - :stop/:suspend - screen resize
* ui: Implement set_{title,icon}Thiago de Arruda2015-01-14
|
* test: Add Screen.debug for inspecting screens of hanging testsThiago de Arruda2015-01-13
|
* ui: Add 'rgb' parameter to ui_attachThiago de Arruda2015-01-13
| | | | When set to false, nvim will send cterm color numbers with `highlight_set`.
* test: Remove unnecessary command from highlight_specThiago de Arruda2015-01-13
|
* ui: Fix ui resizing and change some method namesThiago de Arruda2015-01-13
|
* ui: Add update_fg/update_bg methodsThiago de Arruda2015-01-13
| | | | | It is necessary to notify the UI when the default background/foreground colors change in order to render correctly.
* test: Fix clear/eol_clear in screen.luaThiago de Arruda2015-01-13
| | | | These functions need to operate on the current the scroll region.
* Revert "[WIP] "abstract_ui" fixes and improvements"Justin M. Keyes2015-01-12
|
* ui: Reimplement `:suspend` command for remote UIs.Thiago de Arruda2015-01-12
| | | | | | - Remove suspend method from the UI protocol - Handle `:suspend` by disconnecting the last channel that sent a request to nvim.
* ui: Add 'rgb' parameter to ui_attachThiago de Arruda2015-01-12
| | | | When set to false, nvim will send cterm color numbers with `highlight_set`.
* test: Remove unnecessary command from highlight_specThiago de Arruda2015-01-12
|
* ui: Fix ui resizing and change some method namesThiago de Arruda2015-01-12
|
* ui: Add update_fg/update_bg methodsThiago de Arruda2015-01-10
| | | | | It is necessary to notify the UI when the default background/foreground colors change in order to render correctly.
* test: Fix eol_clear in screen.luaThiago de Arruda2015-01-10
| | | | | It should only clear to the end of the current scroll region(this is the behavior expected by nvim)
* input: Recognize mouse events for abstract_uiThiago de Arruda2014-12-10
|
* test: Add screen test facilityThiago de Arruda2014-12-09
- Add screen.lua which implements a remote screen to verify screen state by tests under functional/ui - Add some basic screen/highlight tests