aboutsummaryrefslogtreecommitdiff
path: root/test/functional/plugin
Commit message (Collapse)AuthorAge
* build: Target luacheck HEAD.Justin M. Keyes2016-11-17
| | | | | | | | | | | | https://github.com/mpeterv/luacheck/pull/81#issuecomment-261099606 > If you really want to use bleeding-edge version you should get the > rockspec from master branch, not a fixed commit ... > The correct way to install from a specific commit is cloning that > commit and running "luarocks make" from project directory. The reason > is that running "install" or "build" on an scm rockspec fetches > sources from master but uses build description from the rockspec > itself, which may be outdated.
* CheckHealth: Include v:throwpoint in error message (#5575)Tommy Allen2016-11-12
| | | | | | | | | | * health.vim: Include v:throwpoint in error message * health/provider.vim: Check for ruby executable * health/provider.vim: Combine subprocess stdout and stderr * test: Updated CheckHealth test
* CheckHealth: more checksJustin M. Keyes2016-10-25
|
* health.vim: Show results incrementally.Justin M. Keyes2016-09-05
| | | | | | | | Also: - improve precision of "No healthcheck found" - fix SUGGESTIONS syntax group definition - fix indentation of SUGGESTIONS
* api: consistently use nvim_ prefix and update documentationBjörn Linse2016-08-31
|
* Mark some functional tests as pending in WindowsRui Abreu Ferreira2016-08-26
|
* CheckHealth: Accept [plugin1 [, plugin2 [, ...]]] args.Justin M. Keyes2016-08-21
| | | | | | | | | To healthcheck the "foo" plugin: :CheckHealth foo To healthcheck the "foo" and "bar" plugins: :CheckHealth foo bar To run all auto-discovered healthchecks: :CheckHealth
* CheckHealthJustin M. Keyes2016-08-21
| | | | | | | - Overlay markdown syntax/filetype, don't invent new filetypes/syntaxes. - migrate s:check_ruby() - s:indent_after_line1 - Less-verbose output
* CheckHealthTJ DeVries2016-08-21
| | | | | | | | | | | | | | - Use execute() instead of redir - Fixed logic on suboptimal pyenv/virtualenv checks. - Move system calls from strings to lists. Fixes #5218 - Add highlighting - Automatically discover health checkers - Add tests Helped-by: Shougo Matsushita <Shougo.Matsu@gmail.com> Helped-by: Tommy Allen <tommy@esdf.io> Closes #4932
* tests: don't ignore highlights in various testsBjörn Linse2016-08-14
|
* functests: Fix matchparen_spec.luaZyX2016-06-17
|
* functests: Check logs in lua codeZyX2016-06-10
| | | | | | It is otherwise impossible to determine which test failed sanitizer/valgrind check. test/functional/helpers.lua module return was changed so that tests which do not provide after_each function to get new check will automatically fail.
* Merge pull request #4654 from KillTheMule/testlintJustin M. Keyes2016-05-06
|\ | | | | Satisfy testlint.
| * Satisfy testlint.KillTheMule2016-04-28
| | | | | | | | For that, make luatest ignore the preload.lua files.
* | test: matchparen_spec.luaKillTheMule2016-04-27
|/ | | | Covers vim-patch 7.4.1296
* functests: Make json_functions_spec use new NIL where appropriateZyX2016-04-18
|
* runtime/msgpack: Add support for special valuesZyX2016-04-18
|
* Update lua client to 0.0.1-24Thiago de Arruda2016-04-13
| | | | | The new version of the lua client uses libmpack as a backend, and some test scripts had to be updated to reflect that.
* tests: update tests to use [gs]et_lines instead of [gs]et_line_sliceBjörn Linse2016-04-01
|
* Normalize nan/-nan in plugin/msgpack_spec.luaThiago de Arruda2016-03-07
| | | | | | | -NaN doesn't exist in the IEEE 754 spec, it is a hardware-specific detail abstracted away by luajit(and not by lua or nvim), so there's no need to test it. Normalize all tests that involve -nan so the suite will be compatible with both Lua and Luajit.
* Test: remove artifacts from root directoryMarco Hinz2015-12-01
| | | | | | | | | The tests would leave the following test files in the root directory: Xtest-functional-plugin-shada.shada Xtest-functional-plugin-shada.shada.tmp.f Clean them up in teardown().
* Merge pull request #3581 from ZyX-I/fix-shadaFelipe Morales2015-11-23
|\ | | | | Store last search direction when writing ShaDa files
| * shada: Also store last search directionZyX2015-11-23
| | | | | | | | | | | | | | | | | | | | Note: it looks like viminfo files do not store search direction intentionally. After reading viminfo file search direction was considered to be “forward”. Note 2: all files created on earlier Neovim version will automatically receive “forward” direction. Fixes #3580
* | test/functional: clean up according to luacheck (part 2)Marco Hinz2015-11-23
|/
* runtime: Add shada.vim syntax fileZyX2015-11-01
|
* runtime: Add [ft]plugin/shada.vim files that automatically open .shadaZyX2015-11-01
|
* runtime: Add autoload/shada.vim helper fileZyX2015-11-01
| | | | Contains most of the logic
* functests: Do not run some tests if there is no -NaNZyX2015-11-01
|
* runtime: Add autoload/msgpack.vim helper fileZyX2015-11-01