Add test layer

[Fetz]

PR Prelude

Thank you for working on SpaceVim! :)

Please complete these steps and check these boxes before filing your PR:

• I have read and understood SpaceVim's CONTRIBUTING document.
• I have read and understood SpaceVim's CODE_OF_CONDUCT document.
• I have updated the Following-HEAD page for this PR.
• I understand my PR may be closed if it becomes obvious I didn't actually perform all of these steps.

Why this change is necessary and useful?

[Please explain in detail why the changes in this PR are needed.]
This layer allow to run easily tests without getting out of Vim.

I used as example this commit: afcf906

Related issues: https://github.com/SpaceVim/SpaceVim/issues/2099, vim-test/vim-test#316

Done

• add English docs test layer
• add on English list layer docs, the test layer
• add to doc/SpaceVim.txt the new layer
• add layer to autoload/SpaceVim/layers the test.vim layer

Missing

• add Chinese docs test layer
• add on Chinese list layer docs, the test layer

[codecov]

Codecov Report

Merging #2101 into master will increase coverage by 0.14%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #2101      +/-   ##
==========================================
+ Coverage    25.6%   25.75%   +0.14%     
==========================================
  Files         276      268       -8     
  Lines       13969    13383     -586     
==========================================
- Hits         3577     3447     -130     
+ Misses      10392     9936     -456

[wsdjeg]

I have tried this layer.

1. why vim-test use :!cmd instead of job API. Maybe I will fork this plugin. and make some changes. an option for change how test is runner and how to diaplay stdout will be better.

2. instead of changing statusline, provide a statusline API will be better.

[Fetz]

@wsdjeg thanks for trying the layer.

Regarding the point 1,2 I can't answer those questions since I'm neither a contributor/collaborator of vim-test and as well I'm not so knowledgable with Vim/NeoVim at the moment, maybe in the future :).

I think would be better to ask those questions on their repo issues.

If you fork and for some reason it can't go to the upstream, I can change it to point to your plugin instead.

By the way, one thing that I wanted to have (still looking for some good alternative) is a tool to alternate between code and the tests. I tried to use https://github.com/uptech/alt but it wasn't working for all the cases. There are some similar plugins or possible solutions on this stackoverflow https://stackoverflow.com/questions/9400966/is-there-a-vim-plugin-for-ruby-which-provides-a-switch-to-from-test-command-ou but they don't look ideal or limited to only ruby

[wsdjeg]

@Fetz SpaceVim has already include this plugin https://github.com/tpope/vim-projectionist

with this plugin, you can manager the your project via .projections.json in the root of your project.

after that, you can use command :A to jump between src and test file.

[Fetz]

@wsdjeg I could add a new mapping to this layer if makes sense

Mode	Key	Description	Function
normal	SPC k t	toggle between test and implementation	:A

[wsdjeg]

we have already provide key binding for this feature as I know, it should be SPC j a in current version of SpaceVim.

I want to release v0.9.0 in one mouth, I am not sure if we should merged this layer before this release, as I need to rewrite some api of vim-test.

[wsdjeg]

can you fix the conflictiong files? I will merge this PR.

[wsdjeg]

Thanks.

[Fetz]

You welcome!