let me type just rspec #14

dchelimsky opened this Issue Mar 16, 2010 · 5 comments


None yet

2 participants


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.

benrady commented May 7, 2010

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.


@dchelimsky dchelimsky added a commit that referenced this issue Jul 3, 2011
@dchelimsky dchelimsky 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)
@timcharper timcharper pushed a commit to timcharper/rspec-core that referenced this issue Aug 19, 2011
@dchelimsky Ben Rady + dchelimsky Run specs in spec directory (if exists) by default
Closes #14
Closes #12
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment