cypress-har-generator

The Cypress plugin for generating HTTP Archive (HAR) files is a tool that allows developers and QA engineers to capture detailed information about network requests made during the execution of Cypress tests.

Advantages:

• Detailed visibility into network requests including WebSocket frames, Server-Sent Events (SSE), and more.
• Ability to replay network requests in a web development tool.
• Easy integration with Cypress

Why it is important

• Improves the performance and stability of your application
• Quickly troubleshoot issues with network requests
• Saves a significant amount of time and effort in debugging and troubleshooting network issues.

The plugin allows you to record network requests from multiple targets such as pages, workers, and pop-ups, which allows you to get a more comprehensive view of your application's network activity. This is especially useful for debugging and troubleshooting issues that may be related to multiple sources.

Table of contents

• Install
• Setting Up the Plugin
• Generating a HAR File
• Commands
  • recordHar
  • saveHar
  • disposeOfHar
• Example Usage
• License

Install

To install the plugin as development dependency, run the following command:

1$ npm i --save-dev @neuralegion/cypress-har-generator

✴ For details about changes between versions, and information about updates on previous releases, see the Releases tab on GitHub: https://github.com/NeuraLegion/cypress-har-generator/releases

Setting Up the Plugin

To use the plugin, you'll need to update the cypress/plugins/index.js file as follows:

1const { install } = require('@neuralegion/cypress-har-generator');
2
3module.exports = on => {
4  install(on);
5};

If you're using Cypress version 10.0.0 or higher, you'll need to update your cypress.config.js file as follows (for details see the migration guide):

1const { defineConfig } = require('cypress');
2const { install } = require('@neuralegion/cypress-har-generator');
3
4module.exports = defineConfig({
5  e2e: {
6    setupNodeEvents(on) {
7      install(on);
8    }
9  }
10});

✴ setupNodeEvents can be defined in either the e2e or component configuration

⚠ Please note that the setupNodeEvents does not support multiple on event listeners without overwriting previously defined listeners. To work around this issue, you can either call the install function at the end of the setupNodeEvents function, or use the deprecated ensureBrowserFlags as follows:

1const { defineConfig } = require('cypress');
2const {
3  install,
4  ensureBrowserFlags
5} = require('@neuralegion/cypress-har-generator');
6
7module.exports = defineConfig({
8  e2e: {
9    setupNodeEvents(on) {
10      install(on);
11      on('before:browser:launch', (browser = {}, launchOptions) => {
12        ensureBrowserFlags(browser, launchOptions);
13        return launchOptions;
14      });
15    }
16  }
17});

For more information, see this GitHub issue.

Next, add the following line to your cypress/support/index.js file to register commands that perform the manipulation with a HAR file:

1require('@neuralegion/cypress-har-generator/commands');

✴ Starting from Cypress version 10.0.0, supportFile is set to look for the following file: cypress/support/e2e.js by default.

Generating a HAR File

To generate a HAR file, you'll need to include the following code in your test file(s):

1describe('my tests', () => {
2  before(() => {
3    // start recording
4    cy.recordHar();
5  });
6
7  after(() => {
8    // save the HAR file
9    cy.saveHar();
10  });
11});

By default, the plugin will save the generated HAR file to the root of your project with a file name that includes the current spec's name (e.g. {specName}.har).

You can also specify a different destination folder for the generated HAR file by setting the CYPRESS_HARS_FOLDERS environment variable or the hars_folders field in the env object in your Cypress config file:

1{
2  "env": {
3    "hars_folders": "cypress/hars"
4  }
5}

Alternatively, you can pass the hars_folders variable in the CLI using the --env option:

1$ cypress run --browser chrome --env hars_folders=cypress/hars

Finally, to start running your tests, use the following command:

1$ cypress run --browser chrome

🚧 Currently, only Chrome family browsers are supported. But this plugin also works with Electron, you just need to set the remote-debugging-port option when you launch Cypress as follows:

1$ ELECTRON_EXTRA_LAUNCH_ARGS=--remote-debugging-port=9222 cypress run --browser electron

Please refer to the Electron documentation and the Cypress documentation for more information on how to properly configure this switch.

Commands

The plugin provides two main commands for work with HTTP Archive (HAR) files in your Cypress tests: recordHar and saveHar.

recordHar

Starts recording network logs. All network requests made during the browser session will be recorded.

Here's an example of how to use the recordHar command:

1cy.recordHar();

⚠ The maximum size of a single resource that can be preserved is 10MB. If you need to receive a larger response body, you should adjust the maxResourceBufferSize and maxTotalBufferSize accordingly:

1cy.recordHar({
2  maxTotalBufferSize: 1024 ** 3,
3  maxResourceBufferSize: 100 * 1024 ** 2
4});

However, note that the resource buffer size cannot be greater than 256MB due to the limit for WebSocket connections in Chrome.

You can set the content boolean flag to false to skip loading content field in the HAR.

1cy.recordHar({ content: false });

To include only requests on specific hosts, you can pass an array of patterns specifying a list of hosts using the includeHosts for which to record requests:

1cy.recordHar({ includeHosts: [/.*\.execute-api\.eu-west-1\.amazonaws\.com/] });

To exclude some requests, you can pass an array of patterns specifying a list of paths using the excludePaths to be excluded from the logs:

1cy.recordHar({ excludePaths: [/^\/login/, /logout$/] });

You can also pass an array of MIME types for which to record requests:

1cy.recordHar({ includeMimes: ['application/json'] });

This will record only requests with a MIME type of application/json.

To exclude requests based on their status code, you can use the minStatusCodeToInclude field.

For example, to only include requests that have a status code of 400 or greater, you can pass the minStatusCodeToInclude option as follows:

1cy.recordHar({ minStatusCodeToInclude: 400 });

✴ As of version 6, this option will be removed. Use excludeStatusCodes instead.

Alternatively, you can have more granular control over the requests to exclude by passing an array of status codes you want to exclude from the recorded HAR file.

1cy.recordHar({ excludeStatusCodes: [200, 201, 204] });

⚠ Please note that both options minStatusCodeToInclude and excludeStatusCodes are mutually exclusive.

By default, when you use recordHar command, it will include the blob requests in the recorded HAR file. However, those requests only make sense when they are used on the same page they were created. To exclude the blob requests from the recorded HAR file, set the includeBlobs to false as follows:

1cy.recordHar({ includeBlobs: false });

✴ As of version 6, this flag will be disabled by default.

You can specify the filter option as a path to a module that exports a function (it can be sync or async) to filter out unwanted entries from the HAR. The function should take an Entry object as a parameter and return a boolean indicating whether the entry should be included in the final HAR or not.

Here's an example of how to use the filter option:

1cy.recordHar({ filter: '../support/include-password.ts' });

And here's an example of what the include-password.ts filter module might look like:

1import { Entry } from 'har-format';
2
3export default async (entry: Entry) => {
4  try {
5    return /\"password":/.test(entry.request.postData.text ?? '');
6  } catch {
7    return false;
8  }
9};

In this example, the filter function will only exclude entries in the HAR where the request body contains a JSON object with a password field.

You can also modify the entries before saving the HAR by using the transform option. This option should be set to a path to a module that exports a function, similar to the filter option, to change the Entry object as desired.

1cy.recordHar({ transform: '../support/remove-sensitive-data.ts' });

Here's a simple example of what the remove-sensitive-data.ts module might look like:

1import { Entry } from 'har-format';
2
3const PASSWORD_REGEXP = /("password":\s*")\w+("\s*)/;
4
5export default async (entry: Entry) => {
6  try {
7    // Remove sensitive information from the request body
8    if (entry.request.postData?.text) {
9      entry.request.postData.text = entry.request.postData.text.replace(
10        PASSWORD_REGEXP,
11        '$1***$2'
12      );
13    }
14
15    return entry;
16  } catch {
17    return entry;
18  }
19};

The function should take an Entry object as a parameter and return the modified.

In this example, the transform function will replace any occurrences of password with *** in the request body of each entry.

✴ The plugin also supports files with .js, .mjs and .cjs extensions.

By default, the path is relative to the spec folder. But by providing a rootDir it will look for the module in the provided directory:

1cy.recordHar({
2  filter: 'cypress/support/include-password.ts',
3  rootDir: Cypress.config('projectRoot')
4});

saveHar

Stops recording and saves all requests that have occurred since recordHar was run to a HAR file. By default, the file is saved to the root of the project with a file name that includes the current spec's name (e.g. {specName}.har).

1cy.saveHar();

You can pass a file name to change the default naming behavior.

1cy.saveHar({ fileName: 'example.com.har' });

You can customize a destination folder overriding any previous settings:

1cy.saveHar({ outDir: './hars' });

You can also pass the waitForIdle option to wait for all pending requests to complete before saving the HAR file:

1cy.saveHar({ waitForIdle: true });

This option is false by default. When set to true, the plugin will monitor the count of pending requests and wait for it to reach zero before proceeding with saving the HAR file. This ensures that all responses have been received and the data in the file is complete and accurate.

Additionally, you can pass the maxWaitDuration option to specify the maximum time to wait for the pending requests to complete:

1cy.saveHar({ waitForIdle: true, maxWaitDuration: 20000 });

The maxWaitDuration option is set to 5000 milliseconds by default, meaning it will wait for 5 seconds until all pending requests have completed.

You can also pass the minIdleDuration option to specify the minimum duration in milliseconds to wait for the network idle during the maxWaitDuration time. The network is idle if there are no pending requests during this time.

1cy.saveHar({ waitForIdle: true, minIdleDuration: 1000 });

The minIdleDuration option is set to 100 milliseconds by default.

disposeOfHar

Stops the ongoing recording of network requests and disposes of the recorded logs, which will be not saved to a HAR file.

You may use this command if you have started recording network logs with recordHar command, but you decide to refuse to save the recorded logs to a HAR file. Here's an example of how you might use this command to dispose of the HAR:

1describe('my tests', () => {
2  beforeEach(() => {
3    // start recording
4    cy.recordHar();
5  });
6
7  afterEach(function () {
8    const { state } = this.currentTest;
9    if (state === 'passed') {
10      // decide not to save the recorded logs
11      cy.disposeOfHar();
12    }
13  });
14});

Example Usage

To generate a HAR file during your tests, you'll need to include the recordHar and saveHar commands in your test file(s). Here's an example of how you might use these commands in a test:

1describe('my tests', () => {
2  before(() => {
3    // start recording
4    cy.recordHar();
5  });
6
7  after(() => {
8    // save the HAR file
9    cy.saveHar();
10  });
11});

You can also generate a HAR file only for Chrome browser sessions, if it is not interactive run, and only if the test has failed:

1describe('my tests', () => {
2  beforeEach(() => {
3    const isInteractive = Cypress.config('isInteractive');
4    const isChrome = Cypress.browser.name === 'chrome';
5    if (!isInteractive && isChrome) {
6      cy.recordHar();
7    }
8  });
9
10  afterEach(function () {
11    const { state } = this.currentTest;
12    const isInteractive = Cypress.config('isInteractive');
13    const isChrome = Cypress.browser.name === 'chrome';
14    if (!isInteractive && isChrome && state !== 'passed') {
15      cy.saveHar();
16    }
17  });
18});

If you're using Cypress version 6.2.0 or higher, you can set up hooks in a single step, eliminating the need to define them in each spec file. To do this, you need to call enableExperimentalLifecycle in addition to install as shown below:

1const { defineConfig } = require('cypress');
2const {
3  install,
4  enableExperimentalLifecycle
5} = require('@neuralegion/cypress-har-generator');
6
7module.exports = defineConfig({
8  e2e: {
9    setupNodeEvents(on, config) {
10      install(on);
11      enableExperimentalLifecycle(on, config);
12    }
13  }
14});

⚠ Please note, to utilize this experimental mechanism for setting up lifecycle, you must either disable the interactive mode or enable the "experimentalInteractiveRunEvents" feature. For more details, see the documentation: https://docs.cypress.io/guides/references/experiments#Configuration

License

Copyright © 2024 Bright Security.

This project is licensed under the MIT License - see the LICENSE file for details.