Closed bruno- closed 10 years ago
vim-vspec itself doesn't take care about where test scripts are located. I guess that you run tests via vim-flavor. If so, create an issue to vim-flavor instead of vim-vspec.
vim-flavor uses prove to summarize test result, and prove looks for the t
directory by default. I followed the convention to simplify things.
Hi @kana , Thank you for the swift response. I have opened a request to vim-flavor project. Closing this issue.
Just a quick feedback: I started using vim-vspec yesterday and was able to get up to speed quickly. It's simple and working great! I love the ability to integrate with travis-ci!
Hi, thank you for writing a great plugin.
I tried naming a test directory 'test' instead of 't', but in this case, specs aren't found. Is there a way to make this work? (btw. I got everything working with a test dir 't', but I find that dir name too obscure).
Thanks for the help!