On Feb 22, 2012, at 10:01 PM, "Patrick J. Collins"
wrote:
> So, I've got the following structure:
>
> # config/application.rb
> config.autoload_paths += ["#{Rails.root}/lib"]
>
> # initializers/core_ext.rb
> require "core_ext/array.rb"
> require "core_ext/hash.rb"
> require "core_ext/numer
So, I've got the following structure:
# config/application.rb
config.autoload_paths += ["#{Rails.root}/lib"]
# initializers/core_ext.rb
require "core_ext/array.rb"
require "core_ext/hash.rb"
require "core_ext/numeric.rb"
require "core_ext/float.rb"
require "core_ext/object.rb"
# lib/
I have a working prototype. However, I am having trouble instrumenting the
automation. Are there existing examples or libraries that execute tests
outside of a console? ___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/
On Feb 22, 2012, at 9:00 AM, Matt Wynne wrote:
>
> On 22 Feb 2012, at 15:41, David Chelimsky wrote:
>
>> On Tue, Feb 21, 2012 at 2:48 PM, Mike Pack wrote:
>>> Yup, I find myself doing this all the time. I think it should be considered
>>> that too deep of a stub chain could be a sign of poor
>
On 22 Feb 2012, at 15:41, David Chelimsky wrote:
> On Tue, Feb 21, 2012 at 2:48 PM, Mike Pack wrote:
>> Yup, I find myself doing this all the time. I think it should be considered
>> that too deep of a stub chain could be a sign of poor
>> abstraction/information hiding. Could lead to bad practi
On Tue, Feb 21, 2012 at 2:48 PM, Mike Pack wrote:
> Yup, I find myself doing this all the time. I think it should be considered
> that too deep of a stub chain could be a sign of poor
> abstraction/information hiding. Could lead to bad practices? On the
> flipside, this would be super helpful when
Yup, I find myself doing this all the time. I think it should be considered
that too deep of a stub chain could be a sign of poor
abstraction/information hiding. Could lead to bad practices? On the
flipside, this would be super helpful when dealing with Railsy stubs
because of long scope chains
