search for: objectmentor

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

...t to the name "testing", Uncle Bob''s recent blog on Acceptance Testing/Unit Testing might prove interesting for those of you grappling with the meaning of Story Runner (which fits in the Acceptance Testing space) vs Spec Runner (which fits in the Unit Testing space). http://blog.objectmentor.com/articles/2007/10/17/tdd-with-acceptance-tests-and-unit-tests Enjoy! Cheers, David

Hi All I''m writing a gem to interact with the todoist JSON API and I''m using mocha to mock the server responses so I don''t have to have a net connection to test and so I don''t need to actually use my own API key anywhere. Mostly I am interested in verifying that a correctly formatted URL has been sent, with the appropriate parameters, e.g API key have been

As I work with Rails TestUnit tests I am reconsidering how to use cucumber features. It seems to me that it might be best to have a coherent view of how to arrange my test suites before I get much further into this. Now, so far I have considered three possibilities: 1. Use features exclusively. Create a feature file for each model, one for each controller and possibly an additional one for

Hello. I want to select an item from a select list and have that result in an ajax call that updates two sections on the page. Here is the code in the controller def create ... render :update do |page| page.replace_html ''list_items'', :partial => ''lists/list_items'' page.replace_html ''add_item'', :partial =>