On 2010-08-24 7:14 PM, David Chelimsky wrote:
On Aug 24, 2010, at 12:34 PM, Phillip Koebbe wrote:
I am trying to use Bundler on a Rails 2.3.8 project and am having a problem
when trying to run my specs. This application was on 2.3.5 until yesterday, and
I switched it to 2.3.8 and all specs p
On Aug 24, 2010, at 12:34 PM, Phillip Koebbe wrote:
> I am trying to use Bundler on a Rails 2.3.8 project and am having a problem
> when trying to run my specs. This application was on 2.3.5 until yesterday,
> and I switched it to 2.3.8 and all specs passed. But after adding Bundler
> (0.9.26),
On Aug 24, 2010, at 11:19 AM, Rafael Uchôa wrote:
> Hi there,
>
> I'm developing a FormBuilder (let's say LabelledFormBuilder), and I
> created a helper called labelled_form_for to put the ":builder =>
> LabelledFormBuilder" in options and call the original form_for, like
> suggested on the Rail
I forgot to mention that I'm using Rails 3.0.rc2 and rspec and rspec-rails
2.0.0.beta.20
Regards
On Tue, Aug 24, 2010 at 6:58 PM, Borja Martín wrote:
> Hi,
> I'm trying to write the specs for a rails plugin.
> The thing is that I don't want to include in my specs the spec_helper
> generated for
I am trying to use Bundler on a Rails 2.3.8 project and am having a
problem when trying to run my specs. This application was on 2.3.5 until
yesterday, and I switched it to 2.3.8 and all specs passed. But after
adding Bundler (0.9.26), rake spec fails because (it appears) files in
config/initi
Hi,
I'm trying to write the specs for a rails plugin.
The thing is that I don't want to include in my specs the spec_helper
generated for the rails application as it will load the whole application
stack and will force me to include all the necessary gems in my plugin
Gemfile when it is supposed to
Hi there,
I'm developing a FormBuilder (let's say LabelledFormBuilder), and I
created a helper called labelled_form_for to put the ":builder =>
LabelledFormBuilder" in options and call the original form_for, like
suggested on the Rails API ( http://liten.be//0EBtc ).
I wrote this test:
[code]
Great David, thank you for your help!
I did look at the docs but did not find that straighaway.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
That did it, thanks David.
On Aug 20, 3:12 pm, David Chelimsky wrote:
> On Aug 20, 2010, at 3:36 AM, George wrote:
>
> > Using this command our specs run with the dot-dot-dot output:
>
> > jruby -X-C -S rake spec SPEC=spec/models/trip_spec.rb
>
> > But how do we make the output verbose? (To see
On Tue, Aug 24, 2010 at 5:19 AM, Alex Pressberg wrote:
> Yes! We do use render in helpers to a great extent and are bitten by the
> "missing template in view path" error too. Any workarounds? Can the view
> path be easily fixed for helper specs in Rspec 1.3?
> Does Rspec 2 already support this?
>
On Aug 24, 2010, at 5:09 AM, nathanvda wrote:
> On Aug 24, 9:56 am, nathanvda wrote:
>> I was using rails 3 rc and rspec beta 19, and everything worked fine.
>> Today i updated and i get errors on the following methods:
>>
>> rendered.should contain("bla")
>>
>> rendered.should have_xpath(//tabl
I rolled back to version 2.0.0.beta.19 and everything is fine again.
On Aug 24, 9:56 am, nathanvda wrote:
> I was using rails 3 rc and rspec beta 19, and everything worked fine.
> Today i updated and i get errors on the following methods:
>
> rendered.should contain("bla")
>
> rendered.should hav
Yes! We do use render in helpers to a great extent and are bitten by the
"missing template in view path" error too. Any workarounds? Can the view
path be easily fixed for helper specs in Rspec 1.3?
Does Rspec 2 already support this?
Cheers, Alex
David Chelimsky wrote:
> On Thu, Jun 4, 2009 at
I was using rails 3 rc and rspec beta 19, and everything worked fine.
Today i updated and i get errors on the following methods:
rendered.should contain("bla")
rendered.should have_xpath(//table//tr)
rendered.should have_selector('#foo')
What should i do?
14 matches
Mail list logo
