I messed with this some more and implemented the idea I mentioned
above:
http://github.com/myronmarston/rspec-core/commit/ec3001f290b091fcdab9fb972d9596dd34a91e4e
I think this is *definitely* a better implementation of
#module_eval_with_args for ruby 1.8.6. It does have the undesirable
side effe
On Aug 21, 2010, at 11:37 AM, narwen wrote:
> I'm wondering what is the elegant way to say to rspec to use capybara
> instead of webrat. Also, I'm not using cucumber.
>
> My project is using:
>
> rails (3.0.0.rc)
> rspec (2.0.0.beta.19)
> capybara (0.3.9)
>
> I had success creating a file: spec
I'm wondering what is the elegant way to say to rspec to use capybara
instead of webrat. Also, I'm not using cucumber.
My project is using:
rails (3.0.0.rc)
rspec (2.0.0.beta.19)
capybara (0.3.9)
I had success creating a file: spec/support/capybara.rb
require 'capybara'
require 'capybara/dsl'
r
On Aug 20, 2010, at 11:22 AM, Rafael Uchôa wrote:
> Hi there,
> I'm using HAML for my views and I want to test them, but I got a
> 'Missing template' exception when I run it.
> I found this topic ( http://urele.com/ua6 ) where David tells to add a
> mapping to deal with haml, but I don't understan
Looking at Ryan B's CanCan for inspiration
require 'rspec'
require 'rspec/autorun'
require 'active_support'
require 'active_record'
require 'action_controller'
require 'action_view'
require 'rails3_plugin_toolbox'
RSpec.configure do |config|
config.mock_with :rr
end
---
require "spec_helper"
I have been thinking that there must be some better ways of doing
Rails plugin development than my current approach. Currently I tend to
have my plugin in one location as a gem and then link to it from some
fresh Rails 3 app, from the vendor/plugins folder, with a symlink.
Then I have to carry arou
