> thanks for reply
> now this is working
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
Hm, make sure you have something like
MySuperApp::Application.configure do
routes.default_url_options = { :host => "test.host", :protocol => 'https' }
end
in your config\environments\test.rb
On Sat, Nov 13, 2010 at 4:01 AM, Steve wrote:
> Thanks, that did it. I still have a nil error when try
Hi
I recently did a coding kata and ran into some strange behaviour. The code is
here[1], the weirdness under the comment "Doesn't work... RSpec bug?".
Basically, all the `subject` / `its(:sequence)` examples seem to work, except
the one split into the two contexts. In this case `its(:sequenc
On Nov 12, 3:11 pm, David Chelimsky wrote:
> On Nov 12, 2010, at 7:23 AM, Ole Morten Amundsen wrote:
>
> > First of all, please direct me into how better to search existing threads
> > in this mailing list.
>
> Not sure what you tried already, but:
Thanks, I didn't know about the google group.
That didn't seem to change anything. I'll have to keep playing with
it, but if you have any other thoughts I'm all for it.
On Nov 13, 5:53 am, Evgeniy Dolzhenko wrote:
> Hm, make sure you have something like
>
> MySuperApp::Application.configure do
> routes.default_url_options = { :host => "tes
I'm still working on getting the basic Rails 2 configuration for RSpec
and Cucumber from the RSpec book up and running.
I've installed the various gems as follows:
$ [sudo] gem install rspec-rails --version 1.3.3
$ [sudo] gem install cucumber-rails --version 0.3.2
$ [sudo] gem install database_cl
We're into some horrible throw-it-and-see-if-it-works loop now, but I
can tell you
here is what I use in my `before` blocks to test the subdomain routing
in controller specs:
request.env.merge!('HTTP_HOST' => 'hi5.test.host')
On Sat, Nov 13, 2010 at 7:54 PM, Steve wrote:
> That didn't seem to ch
We are indeed. There is no request var available in Capybara. I think
that is supposed to be taken care of by Capybara.default_host which I
have set, but still no dice. I see exciting times ahead trying to get
this working.
On Nov 13, 2:31 pm, Evgeniy Dolzhenko wrote:
> We're into some horrible t