Given a ./spec directory, the rspec command could assume that it holds specs and run them without having to type "rspec spec".
This is pretty much worked out - just need to fix a failing cuke.
The blocker on this is that the "rake rcov" task seems to be trying to load the spec suite twice, resulting in a number of "already defined" errors.
Fixed. Submitted a pull request
Hey Ben - I rolled back the auto assumption of a 'spec' directory because it causes all the specs to be run twice when using rcov.
add wip cuke showing how to run a spec with the ruby command
- this passes against 2.6.4, but fails against the current code,
probably related to #379
(which turns out to be a dup of #14)
Run specs in spec directory (if exists) by default