search for: butunclebob

I have a spec: specify "a post with no user id should add a record" do post :edit_or_create, :user => {:login => ''joeschmoe'', :email => ''joe at shmoe.com'', :email_confirmation => ''joe at shmoe.com'', :full_name => ''Joe Schmoe''} assigns[:user].should_not_be_nil

...For some, that results in more tests than others. In approaching BDD, my initial thinking was to write examples for all of the possible behaviours in every context. I''ve had a change of thinking on this. Please check out my blog on it and let me know your thoughts (here or there). http://butunclebob.com/ArticleS.DavidChelimsky.SpecOrganization Thanks, David

So I dig rspec and BDD, of course. I thought that Dave''s Google Video was a great intro () -- even if it was a bit heavy on theory and a bit loose on the nuts and bolts. But I don''t see anyone sufficiently answering the big question: What do you test? How do you define higher level and lower level behaviors that should have tests written for them?

How does a person test private methods? Is there a way to declare them as private, but retain any tests that were written during the initial development? Thanks. -- Posted via http://www.ruby-forum.com/.