On Sep 8, 2013, at 12:41 AM, Emil S emil.so...@gmail.com wrote:
Andre, what you need is Rack::Test, not capybara.
Not sure what you mean here. Capy uses Rack::Test by default:
https://github.com/jnicklas/capybara#selecting-the-driver
--
You received this message because you are subscribed
I meant to say simply use Rack::Test to make the requests while testing,
Capybara isn't useful for interacting with an API directly.
On 8 September 2013 23:43, Tamara Temple tamouse.li...@gmail.com wrote:
On Sep 8, 2013, at 12:41 AM, Emil S emil.so...@gmail.com wrote:
Andre, what you need
I know a lot people may disagree, but I believe that using Cucumber is
counterproductive as writing plain English text and then parsing it with
regular expressions is somewhat overkill and error prone. I think anyone
should use Cucumber only if they have a strong reason to. And some well
known
On Fri, Aug 23, 2013 at 4:15 AM, Ilya Igonkin osd...@gmail.com wrote:
using Cucumber is counterproductive as writing plain English
text and then parsing it with regular expressions is somewhat
overkill and error prone. I think anyone should use Cucumber
only if they have a strong reason to.
So far, I've been using RSpec for testing my Rails apps simply because
that's what railstutorial.org emphasizes.
However, I am in the process of trying out Cucumber. I like the fact that
it's in plain English, and this is an asset for communicating with clients
or other people who aren't
On Aug 22, 2013, at 4:29 PM, Jason Hsu, Android developer
jhsu802...@gmail.com wrote:
So far, I've been using RSpec for testing my Rails apps simply because that's
what railstutorial.org emphasizes.
However, I am in the process of trying out Cucumber. I like the fact that
it's in plain
My rule of thumb : Cucumber for integration testing ( output =
documentation of features ) and RSpec for unit testing ( output =
documentation of code )
On 23 August 2013 03:18, Tamara Temple tamouse.li...@gmail.com wrote:
On Aug 22, 2013, at 4:29 PM, Jason Hsu, Android developer
7 matches
Mail list logo