Hi Emil,
Can you show me that example in cucumber but written in Rspec I been trying
to solve that problem and dont seem to be able to send the parameters in
json to the page using rspec + capybara.
all the best,
Andre
--
You received this message because you are subscribed to the Google
Andre, what you need is Rack::Test, not capybara.
On 8 September 2013 03:54, and...@benjamin.dk wrote:
Hi Emil,
Can you show me that example in cucumber but written in Rspec I been
trying to solve that problem and dont seem to be able to send the
parameters in json to the page using rspec
My personal experience, of course, but the only time I'll ever write
Cucumber features is if plain-english acceptance tests are a requirement.
Otherwise (95% of the time), I'm quite happy with the RSpec/Capybara
combo. The overhead of having to wire together plain-english to regular
On Sat, Aug 24, 2013 at 2:58 AM, Rekha Benada rekha.ben...@gmail.comwrote:
Rspec is a popular framework for unit testing and Cucumber is used for
integration testing and behavior driven development
It's pretty strange to hear since RSpec description is BDD for Ruby. More
than that, recent
I'm a big fan of RSpec, and I use it all the time. But I think Cucumber
wins hands down in generating readable test outputs which can be important
in many scenarios. Let me explain one such scenario which I faced in one of
my projects.
I was working on a Rails API app which would serve as the
Rspec is a popular framework for unit testing and Cucumber is used for
integration testing and behavior driven development
Unit tests with rspec confirm that small, discrete portion continue working
as developers add features.
Integration tests built with cucumber determine wether the
6 matches
Mail list logo
