aboutsummaryrefslogtreecommitdiff
path: root/test/functional/provider
Commit message (Collapse)AuthorAge
* test/python: less-noisy Python skip-messageJustin M. Keyes2018-02-12
| | | | | Developer can use :checkhealth to get more details, don't need to blast the details in the skip-message every time.
* provider/nodejs: check version in Detect()Justin M. Keyes2017-12-17
|
* test: remove inspect test; set NODE_PATH in nodejs_spec.luaJan Edmund Lazo2017-12-17
| | | | | | | | | | | provider#node#can_inspect will fail on some systems because it is common to have old node versions in OS (any Linux OS that has LTS releases) and CI (Travis, Appveyor). NODE_PATH can be trivially set with VimL. Build scripts don't have to set it for the nodejs tests to work. NODE_PATH is optional to begin with and is used only as a workaround for the neovim node.js host.
* ci: nodejs client acceptance-test #7706Jan Edmund Lazo2017-12-17
| | | | | | | | | | | | | | | | | | | | | | | | ci: install nodejs 8 in Appveyor, Travis provider: check node version for debug support Resolve https://github.com/neovim/neovim/pull/7577#issuecomment-350590592 for Unix. provider: test if nodejs in ci supports --inspect-brk nodejs host for neovim requires nodejs 6+ to work properly. nodejs 6.12+ or 7.6+ is required for debug support via `node --inspect-brk`. provider: run cli.js of nodejs host directly npm shims are useless because the user cannot set node to debug mode via --inspect-brk. This is problematic on Windows which use batchfiles and shell scripts to compensate for not supporting shebang. The patch uses `npm root -g` to get the absolute path of the global npm modules. If that fails, then the user did not install neovim npm package globally. Use that absolute path to find `neovim/bin/cli.js`, which is what the npm shim actually runs with node. glob() is for a simple file check in case bin/ is removed because the npm shims are ignored now.
* doc: replace ":CheckHealth" with ":checkhealth"Justin M. Keyes2017-10-17
|
* functests: Replace check_provider -> missing_provider with err reportZyX2017-05-13
|
* functests: Test invalid behaviourZyX2017-05-13
| | | | Test correctly fail for oneline ruby, python and python3.
* api: Do not truncate errors <1 MB. #6237Sander Bosma2017-04-23
| | | | Closes #5984
* rplugin: Call s:LoadRemotePlugins() on startup.Justin M. Keyes2017-03-11
| | | | | | | | | | Dispense with the FuncUndefined/CmdUndefined quasi-optimization. If there are no rplugins, plugin/rplugin.vim takes less than 1ms. Closes #5821 Closes #6250 Helped-by: Qiming zhao <chemzqm@gmail.com>
* Merge #4980 'Support legacy `:ruby` commands'.Justin M. Keyes2016-07-10
|\
| * Add :ruby, :rubyfile, and :rubydo ex commandsAlex Genco2016-07-02
|/
* 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.
* eval: Stop executing *eval() function at errorZyX2016-05-27
| | | | | Fixes #4822 Closes #4823
* test: remote/define.vim: Add some spice.Justin M. Keyes2016-04-18
|
* test: formatCase Nelson2016-04-18
|
* test: remote/define.vim: rangeCase Nelson2016-04-18
|
* test/functional: clean up according to luacheck (part 1)Marco Hinz2015-11-23
|
* Ensure a session is running before attempting to do Python detection.John Szakmeister2015-11-04
|
* test: Check for installed Python module with Vimscript function.Florian Walch2015-09-27
| | | | | | Use the existing Vimscript function provider#pythonx#Detect() to determine whether the Neovim Python module is installed and Python 2/3 tests can be run.
* test: move runtime/autoload/* to provider/Justin M. Keyes2015-08-09
- Organize tests by logical function, not the literal impl location. - Avoid deep nesting / hyper-hierarchy.
generated by cgit (git 2.34.1) at 2025-06-24 02:38:05 +0000