similar to: Named routes problem... more rails than rspec

Hi -- I am just getting to grips w/ view specs, and am having an issue with mock_model not stubbing the mocked model''s attributes. For instance, I have the following: <CODE> before do @input_timesheet = mock_model( InputTimesheet ) assigns[:input_timesheet] = @input_timesheet end it "should display a table element" do render

I find myself doing this kind of thing a lot in Controller Specs: @vacancy = mock_model(Vacancy) @vacancy.stub!(:reference) @vacancy.stub!(:title) @vacancy.stub!(:created_at) @vacancy.stub!(:updated_at) @vacancy.stub!(:body) @vacancy.stub!(:contract) @vacancy.stub!(:location) @vacancy.stub!(:salary) @vacancy.stub!(:benefits)

Hey, I just ran into a situation where I would like to expect a method call with an argument I know and another one, which is a random number. I think mocking up the rand method is somehow ugly so I thought maybe this is the first time where I can take something from Java to Ruby ;) Java''s EasyMock mocking library knows things like "anyObject()" and "anyInteger()" in

Never seen the error above before, code: describe "edit action" do it "edit action should render edit template" do food = Food.create(:name=>''mooo'') # Food.any_instance.stubs(:valid?).returns(true) get :edit, :id => food.id response.should render_template(:edit) end end -------------- next part

Hi, My application relies on request.domain for doing its job. The problem I am encountering, is that when running tests, request.domain returns "test.host", how can I change that so that it returns "mysite.com"? Thanks in advance. -- Posted via http://www.ruby-forum.com/.

I am facing strange problem. I have an object @part=MainPart.find(:all) 1. @part.each_with_index do |mainpart,index| 2. <p><%= mainpart.object_id%></p> 3. end Here problem is that object_id is reserved for rails. Here object_id field in my table . Now i want to get value <%= mainpart.object_id%> is giving GARBAGE VALUE. Is there any solution apart from

I am using mock_model in my tests, and I encountered a situation where my stub is failing. Here''s the scenario: Controller: @locations = Location.al(:bounds=>bounds)l @locations.sort_by_distance_from([bounds.center.lat,bounds.center.lng]) Rspec: @location = mock_model(Location) Location.stub(:all).and_return([@location])

This came up from an other issue where I needed to go check something in test::unit. Immediately when I dropped into the debugger in test::unit I saw something I have been missing: test unit by default shows a number of lines of code. Is there a way to make the rspec debugger do this? I am not sure if it is just me, but seems to me that when I moved to rspec, certain things which seemed to be

Hi guys. I''m setting an expectation on a class method. For some reason, the method isn''t being stubbed, and the expectation isn''t seeing the call. In KeywordListsController#create, I call the private method #create_keywords_and_associate, which calls AdSenseHeavenParser#parse . Thus, some of my specs set an expectation on AdSenseHeavenParser#parse . However, that

I finally plunked down for the beta RSpec bundle and I''m working through the initial example. Although I''m a fairly experienced RSpec user, I''m stlll learning new tricks. Anyway, I''m going though the mastermind example, and everything is going well, except that I decided to also try out the Textmate bundle for Cucumber. I decided to use Ben Mabey''s

I''m now in the process of facing converting a rails app to use Ruby 1.9.1. Has anyone figured out how to use 1.9 with the RSpec bundle in textmate and preferably how to switch back and forth? -- Rick DeNatale Blog: http://talklikeaduck.denhaven2.com/ Twitter: http://twitter.com/RickDeNatale WWR: http://www.workingwithrails.com/person/9021-rick-denatale LinkedIn:

I''m having a lot of trouble stubbing out an association extension for some view tests. Example rails code modeling a music album: class Album < ActiveRecord::Base has_many :songs do def streamable find(:all, :conditions => ''streamable = 1'') end end end So for a given Album instance (say @album), I need to be able to stub both

Passenger configuration selects which ruby executable to use via a global configuration variable (at least for Apache, I assume it''s the same for Nginx). I''m in a situation where I''ve got at least one rails app I''d like to run on 1.9 while others remain on 1.8. This is for my development machine running OS X 10.6. Normally I just use the Passenger PrefPane,

I''ve found these two snippets of code useful and would love some feedback. first, .should_have_valid_associations usage: context "A new Product" do specify "should have valid associations" do @product.should_have_valid_associations end end code: (thanks to Wilson/Defiler for converting to rspec) module Spec module Expectations module Should

Hey all, I get an undefined method `join'' for #<String NoMethodError. student.rb has_one :student_fail attr_accessor :student_fail_attribute #controller def student_fail @student = @student.find params[:id] def update_student_fail @student.build_student_fail params[:student][:student_fail_attribute] if @student.save #view form_for @student do |f|

Hi, i try to understand how plugins work in detail. Often you see stuff like: class Post < ActiveRecord::Base   acts_as_commentable end I wonder what''s happen all there. What kind of language-feature is behind this call "acts_as_commentable" ? In my opinion you need some kind of extend or include to extend the functionality of a model. And exactly this is which i found

I have upgraded from 1.2.6 to 2.0.1 and successfully passed all my test and manual testing. Everything seems to be working correctly. My application is pretty vanilla and so there where few complications. Question is, should I do another point upgrade (and if so, which point to upgrade to next) or is it safe (and prudent) to just go straight on to the current version (2.3.x). Advise would be

Along the same lines as the default javascript library discussion [1], why don''t we switch the default test library to RSpec? The stats [2] posted by Xaviar in the other thread seem to support that RSpec is the preferred way to test. [1] http://groups.google.com/group/rubyonrails-core/browse_thread/thread/e9b9cf2233d9a59b [2] http://survey.hamptoncatlin.com/survey/stats -- You received

Why are there more web design users using PHP instead of using Rails? Is there an advantage using PHP over Rails? Thanks -- Posted via http://www.ruby-forum.com/.

i just ran into a problem with some test, and i am not exactly sure why, but the difference happened when i changed my model validation from: validate :custom_validation to: validate_on_create :custom_validation can someone give me any ideas on where in the chain the validation takes place? thanks! -- Posted via http://www.ruby-forum.com/.