On 28 Aug, 21:21, Toni Tuominen wrote:
> Have selector is a webrat matcher. If you're not using webrat you
> can't use it. Capybara's matcher is have_css. I suggest you take a
> look at capybara docs.
>
> - Toni
Aha, that makes perfect sense Toni. Thanks!
Daniel
_
Have selector is a webrat matcher. If you're not using webrat you
can't use it. Capybara's matcher is have_css. I suggest you take a
look at capybara docs.
- Toni
On Sat, Aug 28, 2010 at 9:59 PM, Justin Ko wrote:
>
>
> On Aug 28, 2:44 pm, Daniel Lidström wrote:
>> On 28 Aug, 19:32, David Chelim
On Aug 28, 2:44 pm, Daniel Lidström wrote:
> On 28 Aug, 19:32, David Chelimsky wrote:
>
> > On Aug 28, 2010, at 11:33 AM, Justin Ko wrote:
>
> > > Did you remove webrat from the Gemfile?
>
> > That won't help with beta.19, which has a hard dependency on webrat.
> > beta.20 does not, so you can
On 28 Aug, 19:32, David Chelimsky wrote:
> On Aug 28, 2010, at 11:33 AM, Justin Ko wrote:
>
> > Did you remove webrat from the Gemfile?
>
> That won't help with beta.19, which has a hard dependency on webrat. beta.20
> does not, so you can choose between webrat and capybara.
Thanks for the respo
On Aug 28, 2010, at 11:33 AM, Justin Ko wrote:
>
>
> On Aug 28, 6:59 am, Daniel Lidström wrote:
>> On 28 Aug, 04:13, Justin Ko wrote:
>>
>>
>>
>>> I would suggest switching to capybara.
>>
>> Hi Justin,
>>
>> I tried changing a part of my Gemfile to this:
>>
>> group :development, :test
On Aug 28, 6:59 am, Daniel Lidström wrote:
> On 28 Aug, 04:13, Justin Ko wrote:
>
>
>
> > I would suggest switching to capybara.
>
> Hi Justin,
>
> I tried changing a part of my Gemfile to this:
>
> group :development, :test do
> gem 'rspec-rails', '>= 2.0.0.beta.19'
> gem 'capybara'
> end
I think you're having this problem:
http://github.com/rspec/rspec-rails/issues#issue/140
- Toni
On Sat, Aug 28, 2010 at 1:59 PM, Daniel Lidström wrote:
> On 28 Aug, 04:13, Justin Ko wrote:
>>
>> I would suggest switching to capybara.
>
> Hi Justin,
>
> I tried changing a part of my Gemfile to t
On 28 Aug, 04:13, Justin Ko wrote:
>
> I would suggest switching to capybara.
Hi Justin,
I tried changing a part of my Gemfile to this:
group :development, :test do
gem 'rspec-rails', '>= 2.0.0.beta.19'
gem 'capybara'
end
I am not sure if this is correct or what to do next. I tried "bundle
On Aug 27, 8:44 pm, Justin Ko wrote:
> On Aug 27, 4:12 pm, Daniel Lidström wrote:
>
>
>
>
>
> > Hello,
>
> > I am trying to run my first integration tests of my rails 3
> > application. All tests fail with an error "stack level too deep". The
> > tests are intended to verify the link routes and
On Aug 27, 4:12 pm, Daniel Lidström wrote:
> Hello,
>
> I am trying to run my first integration tests of my rails 3
> application. All tests fail with an error "stack level too deep". The
> tests are intended to verify the link routes and look like this:
>
> dan...@ubuntu/home/daniel/programming
One thing I notice is you have "get '/'" yet you don't have a root
route. You can define a root route like so:
root :to => "pages#home"
Also, you can run your requests by doing "rake spec:requests"
On Aug 27, 4:12 pm, Daniel Lidström wrote:
> Hello,
>
> I am trying to run my first integration t
Hello,
I am trying to run my first integration tests of my rails 3
application. All tests fail with an error "stack level too deep". The
tests are intended to verify the link routes and look like this:
dan...@ubuntu/home/daniel/programming/rails_projects/sample_app$ cat
spec/requests/layout_links
12 matches
Mail list logo
