README

analytics.js-integration-tester

An plugin to easily test an Analytics.js integration.

Installation

$ npm install @segment/analytics.js-integration-tester

Example

Imagine you had an integration that looked like this:

module.exports = createIntegration('Custom')
  .readyOnInitialize()
  .global('_custom')
  .option('apiKey', '')
  .option('track', false);

You can easily assert that all of those properties are there with a familiar API, like so:

var Analytics = require('@segment/analytics.js-core').constructor;
var tester = require('@segment/analytics.js-integration-tester');
var plugin = require('./integration');
var Custom = plugin.Integration;
var analytics = new Analytics();
var custom = new Custom;
analytics.use(tester);
analytics.add(custom);

var Test = createIntegration('Custom')
  .readyOnInitialize()
  .global('_custom')
  .option('apiKey', '')
  .option('track', false);

analytics.validate(Custom, Test);

You can also use the tracking and spying methods to quickly test cases:

analytics.stub(window, '_custom');
analytics.track('Event', { property: true });
analytics.called(window._custom, 'Event', { property: true });

The general pattern we use is to stub the methods in a beforeEach test block, then call an analytics method (track, page, identify, etc.), and then check if some other internal method got called with the correct arguments using analytics.called(method, args...).

API

compare(integration, testIntegration)

Assert that an integration is correctly defined, that it matches the testIntegration's options, globals, configuration, and name.

spy(object, method)

Spy on a method of a host object.

stub(object, method)

Stub a method of a host object. Stubs are different than spies in that they won't pass the arguments through to the original method.

called(spy, [args...])

Assert that a spy was called, optionally with args....

didNotCall(spy, [args...])

Assert that a spy was not called, optional with args....

returned(spy, value)

Assert that a spy was called and returned value.

didNotReturn(spy, value)

Assert that a spy was called and did not return value.

initialize()

Call initialize on the integration.

reset()

Reset the tester. This will call reset on the integration, as well as restore all existing spies.

load(integration, callback)

Assert that the integration load method can load the library, and that loaded properly checks for the libraries existence, then callback(err).

(args...)

Call one of the core analytics methods on the integration with args.... The methods include: alias, identify, group, page, and track.

assert(actual)

Assert that an actual value is truthy.

equal(actual, expected)

Assert that an actual value is equal to an expected value.

notEqual(actual, expected)

Assert that an actual value is not equal to an expected value.

deepEqual(actual, expected)

Assert that an actual value is deeply equal to an expected value.

notDeepEqual(actual, expected)

Assert that an actual value is not deeply equal to an expected value.

strictEqual(actual, expected)

Assert that an actual value is strict (===) equal to an expected value.

notStrictEqual(actual, expected)

Assert that an actual value is not strict (===) equal to an expected value.

throws(fn)

Assert that a fn throws an error.

doesNotThrow(fn)

Assert than a fn does not throw an error.

waitForScripts(callback)

Waits for all script elements to finish loading before calling callback. Often scripts loaded onto the page will add other scripts in order to support their functionality. These scripts can reference globals that we clear after each test, causing them to fail if they load too late.

afterEach(function(done) {
  analytics.waitForScripts(function() {
    myIntegration.reset();
    analytics.reset();
    done();
  });
});

Usage no npm install needed!