Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

webdriverajax

Package Overview
Dependencies
Maintainers
1
Versions
11
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

webdriverajax

Capture and assert HTTP ajax calls in webdriver.io

  • 1.1.0
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
4.9K
decreased by-0.16%
Maintainers
1
Weekly downloads
 
Created
Source

webdriverajax

Travis badge Join the chat at https://gitter.im/chmanie/webdriverajax Capture and assert HTTP ajax calls in webdriver.io

This is a plugin for webdriver.io. If you don't know it yet, check it out, it's pretty cool.

Although selenium and webdriver are used for e2e and especially UI testing, you might want to assess HTTP requests done by your client code (e.g. when you don't have immediate UI feedback, like in metrics or tracking calls). With webdriverajax you can intercept ajax HTTP calls initiated by some user action (e.g. a button press, etc.) and make assertions about the request and corresponding resposes later.

There's one catch though: you can't intercept HTTP calls that are initiated on page load (like in most SPAs), as it requires some setup work that can only be done after the page is loaded (due to limitations in selenium). That means you can just capture requests that were initiated inside a test. If you're fine with that, this plugin might be for you, so read on.

Prerequisites

  • node.js > v0.12 (as we're using native ES6 Promises)
  • webdriver.io v3.x.

Installation

Use npm:

npm install webdriverajax

Usage

Using with wdio

If you use the integrated test-runner (wdio) it's as easy as adding webdriverajax to your wdio.conf.js:

plugins: {
  webdriverajax: {}
}

and you're all set.

Programatic usage

You should require the package and call the config function with your webdriver-instance (client or browser or whatever you call it) before you initialize it with .init(). So for example (using mocha):

var wdajax = require('webdriverajax');

var client = webdriverio.remote({
  desiredCapabilities: {
    browserName: 'firefox'
  }
});

before(function() {
  wdajax.init(client);
  return client.init();
});

Once initialized, some related functions are added to your browser command chain (see API).

Quickstart

Example usage (promise-style):

browser
  .url('http://foo.bar')
  .setupInterceptor() // capture ajax calls
  .expectRequest('GET', '/api/foo', 200) // expect GET request to /api/foo with 200 statusCode
  .expectRequest('POST', '/api/foo', 400) // expect POST request to /api/foo with 400 statusCode
  .expectRequest('GET', /\/api\/foo/, 200) // can validate a URL with regex, too
  .click('#button') // button that initiates ajax request
  .pause(1000) // maybe wait a bit until request is finished
  .assertRequests(); // validate the requests

Get details about requests (generator-style):

yield browser.url('http://foo.bar')
    .setupInterceptor()
    .click('#button')
    .pause(1000);

var request = yield browser.getRequest(0);
assert.equal(request.method, 'GET');
assert.equal(request.response.headers['content-length'], '42');

Supported browsers

It should work with somewhat newer versions of all browsers.

Browser matrix

API

browser.setupInterceptor()

Captures ajax calls in the browser. You always have to call the setup function in order to assess requests later.

browser.expectRequest(method, url, statusCode)

Make expectations about the ajax requests that are going to be initiated during the test. Can (and should) be chained. The order of the expectations should map to the order of the requests being made.

  • method (String): http method that is expected. Can be anything xhr.open() accepts as first argument.
  • url (String|RegExp): exact URL that is called in the request as a string or RegExp to match
  • statusCode (Number): expected status code of the response

browser.assertRequests()

Call this method when all expected ajax requests are finished. It compares the expectations to the actual requests made and asserts the following:

  • Count of the requests that were made
  • The order of the requests
  • The method, the URL and the statusCode should match for every request made

browser.getRequest(index)

To make more sophisticated assertions about a specific request you can get details for a specific request after it is finished. You have to provide the index of the request you want to access in the order the requests were initiated (starting with 0).

  • index (Number): number of the request you want to access

Returns: Promise that resolves to request object:

  • request.url: requested URL
  • request.method: used HTTP method
  • request.response.headers: response http headers as JS object
  • request.response.body: response body (will be parsed as JSON if possible)
  • request.response.statusCode: response status code

browser.getRequests()

Get all captured requests as an array.

Returns: Promise that resolves to an array of request objects.

Running the tests

Firefox has to be installed. Also install selenium standalone via:

node_modules/.bin/selenium-standalone install

then

npm test

Contributing

I'm happy for every contribution. Just open an issue or directly file a PR.

License

MIT

Keywords

FAQs

Package last updated on 05 Feb 2016

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc