Fakeweb rocks.thank you for your efforts.
I'm going to try and pull in that patch soon — seems like a frequently-
encountered problem.
On Jan 13, 1:30 pm, dinshaw <gob...@gmail.com> wrote:
> HI there,
> Is anyone using FakeWeb with Selenium and getting this?
> The calls tohttp://localhost:4444/selenium_client/driverget caught
On Jan 24, 4:38 am, Chris Kampmeier <ch...@kampers.net> wrote:
> Hey dinshaw, we're tracking work on that in a GitHub issue here:http://github.com/chrisk/fakeweb/issues#issue/4
>
> I'm going to try and pull in that patch soon — seems like a frequently-
> encountered problem.
I'm guessing that the issue here is using FakeWeb in cucumber tests
when using selenuim. If so, then you'll be defining what you want
FakeWeb to intercept in your cucumber steps. Now when you fire up
cucumber to run the tests it will start the rails app in a different
thread so it can poke it via a browser. This means that the FakeWeb
stuff is in the wrong thread to have any effect on the app under test
and can only intercept the selenium stuff which pokes the app such as
localhost:4444/selenium_client.
So I'm afraid that I don't think the patch will work for this
situation :(
also posting the same here :
+1,
I have fakeweb to check my tests are not dependent on any external
system.
but i have few javascript tests which runs with culerity, which calls
localhost, and obviously are caught nicely by fakeweb.
If i have a whitelist of websites, i can include it in setup and run
my integration test without hassle.
please update the status of this feature.
Thanks,
Amiruddin Nagri