WIP/RFC: Add base for testing via pytest directly #861
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The main motivation is to being able to use normal/other pytest based tests. Therefore this moves everything from conftest into test_integration itself.
This uses Vim's --remote-expr and --remote-send, which should allow for better testing of some things in the future.
|
Hmm, Vim on Travis is missing |
|
So many conflicts.. \o/
We could either use a more recent Vim (e.g. via Docker - https://github.com/tweekmonster/vim-testbed/ makes this easier), or use Neovim instead (I've done something in this regard for deoplete (Shougo/deoplete.nvim#807)). But I think for now the existing vspec tests are not that bad after all, but the only downside is that you cannot really test a visible popup menu and other corner cases with it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Includes #860.