Please quote when replying.
daze wrote in post #970694:
> Alright. Here's one roadblock.
> So what I understand w/BDD is that I should write all these tests,
> watch them fail, and then code to make the tests pass.
No. Write *one* test, watch it fail, make it pass, refactor as
necessary. Then write the next test. Lather, rinse, repeat.
> But the error
> messages I get from running tests don't provide as much insight as
> doing "rails server" and then seeing whatever error comes up... I
> don't understand how people do this.
Probably by writing more atomic tests. Could you give an example test
that wasn't as useful as you would have liked?
Best,
--
Marnen Laibow-Koser
http://www.marnen.org
marnen@marnen.org
Sent from my iPhone
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
No comments:
Post a Comment