vim-vspec

vim-vspec copied to clipboard

No output when testing with VIM_VSPEC=nvim for certain tests on some environments

9

I am assuming Neovim is partially supported because [this issue](https://github.com/kana/vim-vspec/issues/50) was resolved, let me know if that's incorrect. I have the following tests: ```vim runtime! plugin/fugitive.vim describe 'vspec' it 'test'...

rbong

Hi, I am using your plugin to write tests on a very old plugin. Unfortunately this plugin calls the builtin vim function `expand` in a lot of places. In my...

sixro

Autocmds don't appear to work

5

Hi, It looks like autocmds in tests aren't registered. How to reproduce: - `plugin/foo.vim`: ```vim augroup Bla autocmd! autocmd OptionSet background let g:foo = 'bar' augroup END ``` - `t/foo.vim`:...

runiq

Output friendly failure messages when unexpected errors occur while translating a test script

3

kana

Improve behavior on failure in before/after blocks

1

`:before`/`:after` blocks are not in `:try` blocks. If an exception thrown from one of `:before`/`:after` blocks is not caught, it causes "Bail out". But it would be better to continue...

kana

Support quickfix

1

Currently it's not possible to use quickfix from vspec's output, because there is no assistive information to jump to failed examples.

kana

Make bin/vspec output unbuffered in order to make it possible to create shell wrappers

5

In the solution for #15 a final filter `sed 's/\r$//'` was added in `bin/vspec`. Unfortunately, by default sed buffers its output, so it is no longer possible to add another...

glts

kana

After #33, "Bail out!" is generated for some exceptions even if they were thrown in `:it` blocks. "Bail out!" should not be generated because exceptions in `:it` blocks are fully...

kana

Derived from gh-13. > `:SKIP` has the same problem, but that might be more difficult to solve, because of `command! -bar`.

kana