On Jun 20, 2010, at 1:30 AM, Matt Wynne wrote:
>
> On 19 Jun 2010, at 00:35, David Chelimsky wrote:
>
>> On Jun 18, 2010, at 5:02 PM, Marcelo de Moraes Serpa wrote:
>>
>>> Hi David, thanks for the reply,
>>>
>>> Hmm, considering we have:
>>> 1) The ruby process where the spec is running
>>>
On 19 Jun 2010, at 00:35, David Chelimsky wrote:
> On Jun 18, 2010, at 5:02 PM, Marcelo de Moraes Serpa wrote:
>
>> Hi David, thanks for the reply,
>>
>> Hmm, considering we have:
>> 1) The ruby process where the spec is running
>> 2) A mongrel server serving request (test environment)
>>
>>
What I typically do is wrap any Ajax calls on the client side with
JavaScript objects. Then it is fairly trivial to stub the calls by
just redefining the methods that would normally call the server.
For acceptance testing I would normally just do it end-to-end and not
mock. However, if there is so
On Jun 18, 2010, at 5:02 PM, Marcelo de Moraes Serpa wrote:
> Hi David, thanks for the reply,
>
> Hmm, considering we have:
> 1) The ruby process where the spec is running
> 2) A mongrel server serving request (test environment)
>
> If I call FakeWeb on #1, it won't work on #2, since they are
Hi David, thanks for the reply,
Hmm, considering we have:
1) The ruby process where the spec is running
2) A mongrel server serving request (test environment)
If I call FakeWeb on #1, it won't work on #2, since they are separated
processes and FakeWeb would only monkeypatch Net::HTTP for #1. Or
On Jun 18, 2010, at 12:02 PM, Marcelo de Moraes Serpa wrote:
> One thing that just came to my mind is to fake the requests on the app server
> instance. One simple way to do that would be to just put the FakeWeb call in
> a cucumber / culerity environment file. However, this is far from being
>
One thing that just came to my mind is to fake the requests on the app
server instance. One simple way to do that would be to just put the FakeWeb
call in a cucumber / culerity environment file. However, this is far from
being elegant and is not scalable at all, as the call would be contextless
to
Hello all,
I have an acceptance test that aims to bdd a Google Apps OpenID
authentication feature. This login screen also uses some JS (in order to
switch between the regular / Google OpenID forms). Now, I know this is not
something that would prevent me from using the :rack driver for Capybara,
b
