I am going through the Depot application tutorial in the Agile book and have a question... How is that I can put a reference to my model (i.e. @products Produts.all) in my store controller (or any other for that matter) and it just "knows" about it. To me that seems a lot like global variables which I thought were a no-no. I would expect a require statement at the top or something like that. -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Fri, Aug 20, 2010 at 2:01 PM, Carl Jenkins <lists-fsXkhYbjdPsEEoCn2XhGlw@public.gmane.org> wrote:> I am going through the Depot application tutorial in the Agile book and > have a question... > > How is that I can put a reference to my model (i.e. @products > Produts.all) in my store controller (or any other for that matter) and > it just "knows" about it. > > To me that seems a lot like global variables which I thought were a > no-no. > I would expect a require statement at the top or something like that.In Rails, all controllers know about all models. The controllers are just a way to namespace your app into separate logical pieces. When you do Product.all, Product is a class where all your model methods live, it has nothing to do with any controllers. In Ruby, global variables begin with $. -- Greg Donald destiney.com | gregdonald.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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Hi, I''m a Rails newbie myself, but I think that all required .rb files are automatically required when you boot up your app by invoking "script/server". This probably done in either boot.rb or environment.rb. If you didn''t know, you can invoke "script/console" and create objects from your model in an irb-like command line. I believe it works the same way. Everything that''s required, is automatically required by the framework''s internals. (If I''m wrong, there is probably someone more knowledgable that could clarify further). -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Thanks for the responses!
So to me it seems like Ruby/Rails controllers know about the model;
since Rails "stitches" the view, controllers and model together for
you
I guess that makes sense.
A similar thing that is throwing me for a loop is something like this.
test "should get index" do
get :index
assert_response :success
assert_select ''#columns #side a'' , :minimum => 4
assert_select ''#main .entry'' , 3
assert_select ''h3'' , ''Programming Ruby
1.9''
assert_select ''.price'' , /\$[,\d]+\.\d\d/
end
This is a unit test from the book. The assert_select(s) test the html
response. But, this really confuses me because I see now response
anywhere?
How in the world do the assert statements know of the HTML that was
generated?
--
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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
Philip Hallstrom
2010-Aug-20 19:59 UTC
Re: Re: how does the controller "know" about the model?
> Thanks for the responses! > > So to me it seems like Ruby/Rails controllers know about the model; > since Rails "stitches" the view, controllers and model together for you > I guess that makes sense. > > A similar thing that is throwing me for a loop is something like this. > > test "should get index" do > get :indexThis ''get'' statement makes a request and gets the response. All the other methods know about that response. The details are hidden away...> assert_response :success > assert_select ''#columns #side a'' , :minimum => 4 > assert_select ''#main .entry'' , 3 > assert_select ''h3'' , ''Programming Ruby 1.9'' > assert_select ''.price'' , /\$[,\d]+\.\d\d/ > end > > This is a unit test from the book. The assert_select(s) test the html > response. But, this really confuses me because I see now response > anywhere? > How in the world do the assert statements know of the HTML that was > generated?See here for more... http://guides.rubyonrails.org/testing.html -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Marnen Laibow-Koser
2010-Aug-20 19:59 UTC
Re: how does the controller "know" about the model?
Carl Jenkins wrote:> Thanks for the responses! > > So to me it seems like Ruby/Rails controllers know about the model; > since Rails "stitches" the view, controllers and model together for you > I guess that makes sense. > > A similar thing that is throwing me for a loop is something like this. > > test "should get index" do > get :index > assert_response :success > assert_select ''#columns #side a'' , :minimum => 4 > assert_select ''#main .entry'' , 3 > assert_select ''h3'' , ''Programming Ruby 1.9'' > assert_select ''.price'' , /\$[,\d]+\.\d\d/ > end > > This is a unit test from the book. The assert_select(s) test the html > response. But, this really confuses me because I see now response > anywhere?What would you expect to see that you''re not seeing? Why is this confusing you?> How in the world do the assert statements know of the HTML that was > generated?Why not look at the Test::Unit source code to find out? (BTW, I recommend switching from Test::Unit to RSpec as soon as possible.) Best, -- Marnen Laibow-Koser http://www.marnen.org marnen-sbuyVjPbboAdnm+yROfE0A@public.gmane.org -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Carl Jenkins
2010-Aug-20 20:09 UTC
Re: Re: how does the controller "know" about the model?
Philip Hallstrom wrote:>> Thanks for the responses! >> >> So to me it seems like Ruby/Rails controllers know about the model; >> since Rails "stitches" the view, controllers and model together for you >> I guess that makes sense. >> >> A similar thing that is throwing me for a loop is something like this. >> >> test "should get index" do >> get :index > > This ''get'' statement makes a request and gets the response. All the > other methods know about that response. The details are hidden away... > >> How in the world do the assert statements know of the HTML that was >> generated? > > See here for more... > > http://guides.rubyonrails.org/testing.htmlAhh - thanks for the response(and link) -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Fri, Aug 20, 2010 at 2:59 PM, Marnen Laibow-Koser <lists-fsXkhYbjdPsEEoCn2XhGlw@public.gmane.org> wrote:> (BTW, I recommend switching from Test::Unit to RSpec as soon as > possible.)I recommend staying with Test::Unit. It comes with Rails and works great. -- Greg Donald destiney.com | gregdonald.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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Marnen Laibow-Koser
2010-Aug-23 17:37 UTC
Re: Re: how does the controller "know" about the model?
Greg Donald wrote:> On Fri, Aug 20, 2010 at 2:59 PM, Marnen Laibow-Koser > <lists-fsXkhYbjdPsEEoCn2XhGlw@public.gmane.org> wrote: >> (BTW, I recommend switching from Test::Unit to RSpec as soon as >> possible.) > > I recommend staying with Test::Unit. It comes with Rails and works > great.I''m glad you like it. It is my experience, and that of a large number of other Rails developers, that using RSpec leads to more readable and maintainable tests that focus more on behavior and less on implementation. I don''t see a single advantage of Test::Unit over RSpec (except for the trivial one of its being included with Rails), whereas RSpec has huge advantages over Test::Unit as I outlined above, as well as probably being more beginner-friendly. But we''re losing the topic here, so I''ll stop now.> > > -- > Greg Donald > destiney.com | gregdonald.comBest, -- Marnen Laibow-Koser http://www.marnen.org marnen-sbuyVjPbboAdnm+yROfE0A@public.gmane.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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org 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.
Greg Donald
2010-Aug-23 18:38 UTC
Re: Re: Re: how does the controller "know" about the model?
On Mon, Aug 23, 2010 at 12:37 PM, Marnen Laibow-Koser <lists-fsXkhYbjdPsEEoCn2XhGlw@public.gmane.org> wrote:> It is my experience, and that of a large number > of other Rails developers, that using RSpec leads to more readable and > maintainable testsThey both do the exact same thing. The assertion syntax is nearly identical. RSpec just requires that you type a lot more to do the same job.> that focus more on behavior and less on > implementation. I don''t see a single advantage of Test::Unit over RSpec > (except for the trivial one of its being included with Rails),I personally don''t see the need to type all that extra RSpec syntax when I can type much simpler tests using Test::Unit. If RSpec were so great, why is it still not the default, even with Rails3?> whereas > RSpec has huge advantages over Test::Unit as I outlined above, as well > as probably being more beginner-friendly.What advantages? They both do the _exact same thing_, the main difference is the syntax, one is smaller one is bigger. I''ll stick with the one that requires less work. -- Greg Donald destiney.com | gregdonald.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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org 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.
Marnen Laibow-Koser
2010-Aug-23 18:55 UTC
Re: Re: Re: how does the controller "know" about the model?
Greg Donald wrote:> On Mon, Aug 23, 2010 at 12:37 PM, Marnen Laibow-Koser > <lists-fsXkhYbjdPsEEoCn2XhGlw@public.gmane.org> wrote: >> It is my experience, and that of a large number >> of other Rails developers, that using RSpec leads to more readable and >> maintainable tests > > They both do the exact same thing. The assertion syntax is nearly > identical. RSpec just requires that you type a lot more to do the > same job. > >> that focus more on behavior and less on >> implementation. �I don''t see a single advantage of Test::Unit over RSpec >> (except for the trivial one of its being included with Rails), > > I personally don''t see the need to type all that extra RSpec syntax > when I can type much simpler tests using Test::Unit.I''ve never been able to write or seen anyone else write Test::Unit tests that were actually readable and maintainable. RSpec''s extra syntax encourages a different style of test that is readable.> If RSpec were so > great, why is it still not the default, even with Rails3?Who knows? I can''t speak for the core team. My guess -- and it *is* a guess -- is that it''s because the Rails core team has a bad case of Not Invented Here syndrome in some respects. This is nicely fed into by the assumptions of many Rails developers that the core team''s decisions are perfect and needn''t be questioned.> >> whereas >> RSpec has huge advantages over Test::Unit as I outlined above, as well >> as probably being more beginner-friendly. > > What advantages? They both do the _exact same thing_, the main > difference is the syntax, one is smaller one is bigger.Correct. The RSpec syntax encourages a different style of writing tests.> I''ll stick > with the one that requires less work.So will I. That would be RSpec. The extra typing is trivial compared to the advantage of actually having tests that don''t require elaborate deciphering 6 months later.> > > -- > Greg Donald > destiney.com | gregdonald.comBest, -- Marnen Laibow-Koser http://www.marnen.org marnen-sbuyVjPbboAdnm+yROfE0A@public.gmane.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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org 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.
Greg Donald
2010-Aug-23 19:01 UTC
Re: Re: Re: Re: how does the controller "know" about the model?
On Mon, Aug 23, 2010 at 1:55 PM, Marnen Laibow-Koser <lists-fsXkhYbjdPsEEoCn2XhGlw@public.gmane.org> wrote:> The extra typing is trivial compared > to the advantage of actually having tests that don''t require elaborate > deciphering 6 months later.Test::Unit tests like I write are very easy to decipher: test "should have a first name" do end Seems easy to me. -- Greg Donald destiney.com | gregdonald.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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Marnen Laibow-Koser
2010-Aug-23 19:09 UTC
Re: Re: Re: Re: how does the controller "know" about the model?
Greg Donald wrote:> On Mon, Aug 23, 2010 at 1:55 PM, Marnen Laibow-Koser > <lists-fsXkhYbjdPsEEoCn2XhGlw@public.gmane.org> wrote: >> The extra typing is trivial compared >> to the advantage of actually having tests that don''t require elaborate >> deciphering 6 months later. > > Test::Unit tests like I write are very easy to decipher: > > test "should have a first name" do > > end > > Seems easy to me....and you''ve conveniently left out the hard-to-read assert statements. Got samples I can look at on GitHub or something? I''m curious to see what your tests look like. (Mine are up at http://github.com/marnen .) Best, -- Marnen Laibow-Koser http://www.marnen.org marnen-sbuyVjPbboAdnm+yROfE0A@public.gmane.org Sent from my iPhone> > > -- > Greg Donald > destiney.com | gregdonald.com-- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org 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.
Greg Donald
2010-Aug-23 19:40 UTC
Re: Re: Re: Re: Re: how does the controller "know" about the model?
On Mon, Aug 23, 2010 at 2:09 PM, Marnen Laibow-Koser <lists-fsXkhYbjdPsEEoCn2XhGlw@public.gmane.org> wrote:> ...and you''ve conveniently left out the hard-to-read assert statements.test "should have a first name" do count = User.count( :all ) u = User.new( :email => ''foobar-hcDgGtZH8xNBDgjK7y7TUQ@public.gmane.org'', :password => ''xxxxxxxx'', :lname => ''foobar'', :last_login => Time.now ) assert !u.valid? assert_not_nil u.errors[:fname] assert_equal count, User.count( :all ) u.fname = ''foo'' assert u.save assert_equal count + 1, User.count( :all ) end test "user can login" do get :login assert_response :success post :login, { :login => { :email => ''foo-+RB1Aph5k6s@public.gmane.org'', :password => ''changeme'' } } assert_redirected_to ''/'' assert_not_nil session[:user_id] end What''s so hard to read? -- Greg Donald destiney.com | gregdonald.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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Greg Donald
2010-Aug-23 19:45 UTC
Re: Re: Re: Re: how does the controller "know" about the model?
On Mon, Aug 23, 2010 at 1:55 PM, Marnen Laibow-Koser <lists-fsXkhYbjdPsEEoCn2XhGlw@public.gmane.org> wrote:> Who knows? I can''t speak for the core team. My guess -- and it *is* a > guess -- is that it''s because the Rails core team has a bad case of Not > Invented Here syndrome in some respects. This is nicely fed into by the > assumptions of many Rails developers that the core team''s decisions are > perfect and needn''t be questioned.No, I just don''t see a reason to throw away a perfectly good and working Test::Unit integration in favor of a separate Rspec for purley academic reasons. They do the same thing. The assertions do the same thing. The main difference is one requires more syntax to do the same work. Maybe one day the Rails core team will be as smart as you and switch to Rspec, until then.. -- Greg Donald destiney.com | gregdonald.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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org 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.
Marnen Laibow-Koser
2010-Aug-23 20:43 UTC
Re: Re: Re: Re: Re: how does the controller "know" about the model?
Greg Donald wrote:> On Mon, Aug 23, 2010 at 2:09 PM, Marnen Laibow-Koser > <lists-fsXkhYbjdPsEEoCn2XhGlw@public.gmane.org> wrote: >> ...and you''ve conveniently left out the hard-to-read assert statements. > > test "should have a first name" do > count = User.count( :all ) > u = User.new( :email => ''foobar-hcDgGtZH8xNBDgjK7y7TUQ@public.gmane.org'', :password => > ''xxxxxxxx'', :lname => ''foobar'', :last_login => Time.now ) > assert !u.valid? > assert_not_nil u.errors[:fname] > assert_equal count, User.count( :all ) > u.fname = ''foo'' > assert u.save > assert_equal count + 1, User.count( :all ) > end > > test "user can login" do > get :login > assert_response :success > post :login, { :login => { :email => ''foo-+RB1Aph5k6s@public.gmane.org'', > :password => ''changeme'' } } > assert_redirected_to ''/'' > assert_not_nil session[:user_id] > end > > What''s so hard to read? > >Just about every line of that is hard to read IMHO. I find assert_equal a, b to look cryptic and require me to stop and think every time I see it. By contrast, a.should == b reads more like English (or idiomatic Ruby) and reads quickly and easily for me. (It''s also less typing than the Test::Unit version.) I''ll post an RSpec version for comparison when I''m not typing on my phone. I don''t know why you continue to torture yourself with assert_ syntax. :)> -- > Greg Donald > destiney.com | gregdonald.comBest, -- Marnen Laibow-Koser http://www.marnen.org marnen-sbuyVjPbboAdnm+yROfE0A@public.gmane.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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org 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.
Frederick Cheung
2010-Aug-24 08:14 UTC
Re: how does the controller "know" about the model?
> > Just about every line of that is hard to read IMHO. I find assert_equal > a, b to look cryptic and require me to stop and think every time I see > it. By contrast, a.should == b reads more like English (or idiomatic > Ruby) and reads quickly and easily for me. (It''s also less typing than > the Test::Unit version.)Sounds like a question of habit/personal preference to me - I can''t say I''ve ever found assert_equal hard to understand. Personally I don''t really care whether I write should or assert - you can get the job done either way (although http://pragdave.blogs.pragprog.com/pragdave/2008/03/the-language-in.html is an interesting articles on DSLs trying to be too much like english) and I find the mindset of the developer to be more important that the test syntax used to express it. Fred> > I''ll post an RSpec version for comparison when I''m not typing on my > phone. I don''t know why you continue to torture yourself with assert_ > syntax. :) > > > -- > > Greg Donald > > destiney.com | gregdonald.com > > Best, > > -- > Marnen Laibow-Koserhttp://www.marnen.org > mar...-sbuyVjPbboAdnm+yROfE0A@public.gmane.org > > Sent from my iPhone > -- > Posted viahttp://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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org 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.