Displaying 1 result from an estimated 1 matches for "examples_specdoc".
2007 May 22
3
rspec_on_rails'' spec:doc and dry runs
...ode.com (scanned for a name, didn''t find one =), and end up
writing specs like:
it { @ticket.should validate_presence_of(:name) }
Which results in specdocs such as:
Ticket
- NO NAME (Because of --dry-run)
- NO NAME (Because of --dry-run)
- NO NAME (Because of --dry-run)
The examples_specdoc task for rspec itself, however, doesn''t use --dry-run.
Using dry runs presumably speeds things up significantly, but results
in "broken" docs when using one of rspec''s handiest features. Should
this be considered proper default behavior?
Replacing the task is easy enou...