Home/ Questions/Q 8628453
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-12T08:32:51+00:00

I’m working on integration my rails application with Recurly.js. Before I was making requests

  • 0

I’m working on integration my rails application with Recurly.js.

Before I was making requests to recurly from my server side application, therefore I was able to stub all my integration with excellent VCR gem (https://github.com/myronmarston/vcr) but Recurly.js makes request directly to the service from javascript code using JSONP.

The question is: how to mock these jsonp calls in the integration test?

Currently I’m using rspec + capybara + phantomjs driver (https://github.com/jonleighton/poltergeist)

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The only approach I came up with is on-the-fly javascript patching. As far as the Poltergeist gem has a method to execute javascript right in the test browser, you could apply the following patch to turn Recurly.js into the test mode:

    # The original 'save' function performs JSONP request to Recurly.
# A token is borrowed during the real API interaction.
page.driver.execute_script("""
  Recurly.Subscription.save = function (options) {
    Recurly.postResult('/subscription', { token: 'afc58c4895354255a422cc0405a045b0' }, options);
  }
""")

    Just make a capybara-macros, give a fancy name like ‘stub_recurly_js’ to it and invoke every time before submitting the Recurly.js forms.

    Here is also a link to the original post if you want to dig a little deeper: http://pieoneers.tumblr.com/post/32406386853/test-recurlyjs-in-ruby-using-rspec-capybara-phantomjs

    • 0