Displaying 5 results from an estimated 5 matches for "default_attribution".
2008 Mar 17
4
RSpec''ing model association callbacks
Hi all,
i''m learning rspec and i must admit i really love it.
But at the time i started learning it, i already
developed my models classes and their callbacks.
Now i''m trying to get a 100% coverage of my code but i
cannot reach it because i do not understand how to
spec my callbacks.
Look at this for example:
----------------- User Model
class User < ActiveRecord::Base
 
2008 Jan 11
5
Missing methods
We have a custom implementation of the Mother Object idea. It''s inside  
of a module, basically like this:
module Factory
	%w(account friendship person invitation message asset email_address  
birth).each do |klass|
		eval <<-EOF
		def self.create_#{klass}(attributes = {})
			default_attributes = valid_#{klass}_attributes
			#{klass.camelize}.create!
2007 Dec 28
2
Arity?
...:import_dir_path => @import_dir_path,
                           :import_parent_dir_for_image_dirs =>  
@import_parent_dir_for_image_dirs,
                           :params => params,
                           :import_request => import_request,
                           :default_attribution => @default_attribution,
                           :contributing_user =>  
@contributing_user.id })
I know that @worker_type is set correctly because of the log.
And in the log I get:
...
PastPerfect4ImporterWorker started
past_perfect4_importer_worker started
Schedules for worker loaded...
2006 Mar 24
0
Connecting to SQL server on Mac OS X
I''ve had this problem before on FreeBSD - I fixed it (or worked  
around it) somehow but I can''t remember how.  Also it''s off the  
Google radar but I can''t believe I''m the only person to experience it
I''ve installed FreeTDS and unixODBC from DarwinPorts, along with rb- 
odbc and rb-dbi.  I can connect to my SQL Server from tsql, but  
2007 Dec 06
43
Mocks? Really?
OK, so i''ve played a bit with mocks and mock_models in controller and
view tests and i have a question. Is this statement really correct:
"We highly recommend that you exploit the mock framework here rather
than providing real model objects in order to keep the view specs
isolated from changes to your models."
(http://rspec.rubyforge.org/documentation/rails/writing/views.html