Open jerflan opened 4 years ago
I'm running into this, too--I've got a project which is made up of many separate gems (similar to how https://github.com/rails/rails is layed out), and each gem directory has its own spec
directory. I haven't figured out a way to use this extension with my project even though I'd really like to.
@jerflan did you figure out any solution?
Your environment
vscode-ruby-test-adapter
version: 0.7.1Desired Behavior
This a request for enhancement, not a problem, as the extension works beautifully.
Our two primary apps use components and engines, respectively, to house different functionality and consequently also have their own spec directories. Typically models and other top level classes have specs in
./spec/
but for controllers, presenters, helpers, etc. we often house specs inside of the respective engine or component directory, e.g../engines/admin/spec
I often work out of the top level directory and would love for ruby test explorer to support this, perhaps allow
"rubyTestExplorer.rspecDirectory"
to accept an array of directories, or better yet, grep entire work space for directories namedspec
and pull those into the explorer view. Not sure if this is specific to to this extension or a limitation of the overall vscode test explorer. Will also look at the extension code to see if this is doable but wanted to get this on your radar.Actual behavior
Only able to run and view specs in test explorer when they live in the directory defined by
"rubyTestExplorer.rspecDirectory"
in settings.