On Tue, Aug 4, 2009 at 2:19 PM, Frederick Cheung <[email protected] > wrote:
> > > > On Aug 4, 5:05 am, karthik k <[email protected]> wrote: > > Hi Colin > > > > the name field is made as > > > > validates_uniqueness_of :name > > > > Your test is not consistent: you first assert that post1 is valid, > then you assert that it has an error on the name column - clearly > these cannot both be true. > > Fred hi Fred def test_check_for_uniqueness_name post=County.new(:name=>"mynamed",:description=>"mydesc",:region_id=>"3") assert post.valid?, "post was not valid #{post.errors.inspect}" assert post.save post1=County.new(:name=>"myname",:description=>"mydesc",:region_id=>"4") assert post1.valid?, post1.errors.full_messages assert post1.save end above is my code and worked fine for uniqueness I two name is same then it provides error message else it succeeds plz let me know whether i am right or wrong > > > so please let me know what i did is right or wrong > > though the name is different it is providing the error message > > > > Is this the right way to check uniqueness > > > > I got the information from from > > > > http://railstips.org/2009/1/8/test-or-die-validates-uniqueness-of > > > > Please help > > > > -- > > Karthik.k > > Mobile - +91-9894991640 > > > > > > > > On Sat, Aug 1, 2009 at 6:43 PM, Colin Law <[email protected]> > wrote: > > > > > 2009/8/1 karthik k <[email protected]>: > > > > Hi colin > > > > > > On small help > > > > > > below is the code or checking for uniquness > > > > > > def test_check_for_uniqueness_name > > > > > > post=County.new(:name=>"mynamed",:description=>"mydesc",:region_id=>"3") > > > > assert post.valid?, "post was not valid #{post.errors.inspect}" > > > > > > > post1=County.new(:name=>"sample",:description=>"mydesc",:region_id=>"4") > > > > assert post1.valid?, post1.errors.full_messages > > > > assert_not_nil post1.errors.on(:name) > > > > end > > > > > > when i run unit testing > > > > > > 1) Failure: > > > > test_check_for_uniqueness_name(CountyTest) > [test/unit/county_test.rb:26]: > > > > <nil> expected to not be nil. > > > > > You have said in the test that you expect post1.errors.on(:name) not > > > to be nil, but the test fails because it is in fact nil. Why did you > > > expect it not to be nil? > > > > > Colin > > > --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
