El 15/10/2007, a las 14:21, “David C.” [email protected]
The problem with that approach is this:
Just a bit too long for our taste. So we decided to keep things at the
I actually quite like that proposal, despite the length, because it
groups together all the RSpec stuff in one place, while still
maintaining a separation between the two main parts (the specs and
But I do think “behaviour/specs” is a better choice than “behaviour/
examples” because “specs” seems to have more currency out there; I
think “specs” is much more closely related with RSpec in people’s
minds than “examples”. Say “specs” and people think “RSpec”, but say
“examples” and they could think any number of things.
One alternative: “rspec/examples” (or “rspec/specs”) and “rspec/
stories”. Saves about 4 characters if you’re worried about length,
and also provides some “advertising” for RSpec. I remember when I
first started using RSpec it struck me as odd that the specs were
stored in a folder called “spec” rather than “rspec” or “specs”.
Seeing as stories go in ROOT/stories, perhaps specs should go in
ROOT/specs instead of ROOT/spec.
Well, you could make that change, but it’s probably not all that
important. I certainly wouldn’t oppose it.