Your environment
vscode-ruby-test-adapter version: 0.7.1- Ruby version: 2.6.3
- VS Code version: 1.45.1
- Operating System: Mac OS Mojave 10.14.6
- RSpec version: 3.9.0
Desired 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 named spec 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.
Your environment
vscode-ruby-test-adapterversion: 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/specI 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 namedspecand 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.