I have been trying to spec a Rails Controller for the first time,
having just completed my first View spec.
Having hit a wall trying to spec a controller for my own application,
I have tried to get an example in beta of The RSpec Book to work. I am
however experiencing the same failures. I would a
http://github.com/aslakhellesoy/cucumber/blob/20021e90c892030c1a1b46e2d19024c3719af0ba/History.txt
Thanks Joseph!
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
I'm trying to make sure that my cucumber selenium suite fails if my
Rails app returns any 500 response codes. I'm working on what the best
way to identify this state, but the question I'd like to put to the
list is this: If I want to check for this error condition in an After
or AfterStep,
On 14 May 2009, at 14:20, Phlip wrote:
Matt Wynne wrote:
I've got a reason. You're coupling the tests for this simple little
controller class to all the infrastructure and dependencies needed
to write the record to the database and reload it again. As easy as
Rails makes it for us to man
On Thu, May 14, 2009 at 6:23 AM, Fernando Perez wrote:
>> put :update, :item => 1 etc.
>>
> I tried that but didn't work. I managed to get it working by simply
> doing:
>
> post :update, {:id => 'dummy', :item => {'1' => ...}}
>
> For some reason, I previously tried with :id => 'update' but Rails
Aslak Hellesøy wrote:
>
> If you don't do this, the multiline argument is "dangling". Steps that
> take multiline arguments should be formulated in such a way that
> removing the multiline argument makes the sentence nonsensical.
Yes, I understood that. And I also realized that the solution is
Hello everybody,
I have a problem get cucumber running properly. Runnink jruby -S rake
features ends with:
/Users/alexander/lib/jruby/bin/jruby -I "/Users/alexander/lib/
jruby-1.3.0RC1/lib/ruby/gems/1.8/gems/cucumber-0.3.3/lib:lib" "/Users/
alexander/lib/jruby-1.3.0RC1/lib/ruby/gems/1.8/gems/cucu
On 15/05/2009, at 12:48 AM, aslak hellesoy wrote:
http://github.com/aslakhellesoy/cucumber/blob/173506c4013a7d733c5b4924e7af3dcc49db2218/History.txt
Enjoy!
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/r
http://github.com/aslakhellesoy/cucumber/blob/173506c4013a7d733c5b4924e7af3dcc49db2218/History.txt
Enjoy!
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
On Thu, May 14, 2009 at 7:51 AM, Hugo Barauna wrote:
> Hi guys, I am having a problem with autospec. I upgraded to
> rspec-1.2.6, then I tried to run my specs with autospec. All my specs
> passes (green), until here, that's all ok. The problem is that after
> all my specs have passed, the autospec
Hi guys, I am having a problem with autospec. I upgraded to
rspec-1.2.6, then I tried to run my specs with autospec. All my specs
passes (green), until here, that's all ok. The problem is that after
all my specs have passed, the autospec stops, I mean, it doesn't
continue to run on background. The
Matt Wynne wrote:
I've got a reason. You're coupling the tests for this simple little
controller class to all the infrastructure and dependencies needed to
write the record to the database and reload it again. As easy as Rails
makes it for us to manage our database schemas, gratuitously introd
> put :update, :item => 1 etc.
>
I tried that but didn't work. I managed to get it working by simply
doing:
post :update, {:id => 'dummy', :item => {'1' => ...}}
For some reason, I previously tried with :id => 'update' but Rails
didn't like it.
--
Posted via http://www.ruby-forum.com/.
_
13 matches
Mail list logo
