How to use the replay.networkAccess function in replay

To help you get started, we’ve selected a few replay examples, based on popular ways it is used in public projects.

Secure your code as it's written. Use Snyk Code to scan source code in minutes - no build needed - and fix issues immediately.

github assaf / zombie / test / helpers / first.js View on Github external
const Bluebird  = require('bluebird');
const Browser   = require('../../src');
const Path      = require('path');
const Replay    = require('replay');


// Tests visit example.com, server is localhost port 3003
Browser.localhost('*.example.com', 3003);

// Redirect all HTTP requests to localhost
Replay.fixtures = Path.join(__dirname, '/../replay');
Replay.networkAccess = true;
Replay.localhost('*.example.com');

// Long stack traces when running this test suite
Bluebird.longStackTraces();
github assaf / zombie / test / helpers / index.js View on Github external
// We switch this directory to instrumented code when running code coverage
// report
const Replay    = require('replay');
const Browser   = require('../../src');


Browser.default.silent = true;
// Tests visit example.com, server is localhost port 3003
Browser.localhost('*.example.com', 3003);


// Redirect all HTTP requests to localhost
Replay.fixtures = __dirname + '/../replay';
Replay.networkAccess = true;
Replay.localhost('*.example.com');


module.exports = {
  assert:   require('assert'),
  brains:   require('./brains'),
  Browser:  Browser
};

replay

When API testing slows you down: record and replay HTTP responses like a boss

MIT
Latest version published 6 years ago

Package Health Score

56 / 100
Full package analysis