Cypress terminal report

! 3.x.x is out. Please read the release notes for upgrade path from 2.x.x.

Plugin for cypress that adds better terminal output for easier debugging. Prints cy commands, browser console logs, cy.request and cy.route data.

• looks pretty in console
• logs all commands, requests and browser console logs
• supports logging to files
• option between logging only on failure (default) or always
• options for trimming and compacting logs
• support for multiple and nested mocha contexts
• log commands from before all and after all hooks (with a catch*)

Try it out by cloning cypress-terminal-report-demo.

Note: Currently logs do not appear in the dashboard. If you want to see them go to your CI runner and check the pipeline logs there.

• Requirements
• Install
• Options
• Logging after all and before all hooks
• Logging to files
• Development
• Release Notes

Requirements

• >=3.0.0 requires cypress >=4.10.0
• <3.0.0 requires cypress >=3.8.0

Install

1. Install npm package.

   npm i --save-dev cypress-terminal-report
   

2. Register the output plugin in cypress/plugins/index.js

   module.exports = (on) => {
      require('cypress-terminal-report/src/installLogsPrinter')(on);
   };
   

3. Register the log collector support in cypress/support/index.js

   require('cypress-terminal-report/src/installLogsCollector')();
   

Options

Options for the plugin install

require('cypress-terminal-report/src/installLogsPrinter')(on, options)

options.defaultTrimLength

integer; default: 800; Max length of cy.log and console.warn/console.error.

options.commandTrimLength

integer; default: 800; Max length of cy commands.

options.routeTrimLength

integer; default: 5000; Max length of cy.route, cy.request or XHR data.

options.compactLogs

integer?; default: null; If it is set to a number greater or equal to 0, this amount of logs will be printed only around failing commands. Use this to have shorter output especially for when there are a lot of commands in tests. When used with options.printLogsToConsole=always for tests that don't have any severity=error logs nothing will be printed.

options.outputRoot

string; default: null; Required if options.outputTarget provided. More details.

options.specRoot

string; default: null; Cypress specs root relative to package json. More details.

options.outputTarget

object; default: null; Output logs to files. More details.

options.outputVerbose

boolean; default: true; Toggles verbose output.

options.printLogsToConsole

string; Default: 'onFail'. When to print logs to console, possible values: 'always', 'onFail', 'never' - When set to always logs will be printed to console for successful tests as well as failing ones.

options.printLogsToFile

string; Default: 'onFail'. When to print logs to file(s), possible values: 'always', 'onFail', 'never' - When set to always logs will be printed to file(s) for successful tests as well as failing ones.

options.includeSuccessfulHookLogs

boolean; Default: false. Commands from before all and after all hooks by default get logged only if a command from them failed. This default is in accordance with the defaults on options.printLogsTo* to avoid printing too many, possibly irrelevant, information. However you can set this to true if you need more extensive logging, but be aware that commands will be logged to terminal from these hooks regardless whether there were failing tests in the suite. This is because we can't know for sure in advanced if a test fails or not.

options.collectTestLogs *1

([spec, test, state], [type, message, severity][]) => void; default: undefined; Callback to collect each test case's logs after its run. The first argument contains information about the test: the spec (test file), test (test title) and state (test state) fields. The second argument contains the test logs. 'type' is from the same list as for the collectTypes support install option (see below). Severity can be of ['', 'error', 'warning'].

Options for the support install

require('cypress-terminal-report/src/installLogsCollector')(options);

options.collectTypes

array; default: ['cons:log','cons:info', 'cons:warn', 'cons:error', 'cy:log', 'cy:xhr', 'cy:request', 'cy:route', 'cy:command'] What types of logs to collect and print. By default all types are enabled. The 'cy:command' is the general type that contain all types of commands that are not specially treated.

options.filterLog

null | ([type, message, severity]) => boolean; default: undefined; Callback to filter logs manually. The type is from the same list as for the collectTypes option. Severity can be of ['', 'error', 'warning'].

options.processLog

null | ([type, message, severity]) => string; default: undefined; Callback to process logs manually. The type is from the same list as for the collectTypes option. Severity can be of ['', 'error', 'warning'].

options.collectTestLogs *2

(mochaRunnable, [type, message, severity][]) => void; default: undefined; Callback to collect each test case's logs after its run. The mochaRunnable is of type Test | Hook from the mocha library. The type is from the same list as for the collectTypes option. Severity can be of ['', 'error', 'warning'].

options.xhr.printHeaderData

boolean; default false; Whether to print header data for XHR requests.

options.xhr.printRequestData

boolean; default false; Whether to print request data for XHR requests besides response data.

options.enableExtendedCollector

boolean; default false; Enables an extended collector which will also collect command logs from before all and after all hooks.

Logging after all and before all hooks

Commands from before all and after all hooks are not logged by default. A new experimental feature introduces support for logging commands from these hooks: enableExtendedCollector. This feature is by default disabled as it relies much more heavily on internals of cypress and mocha, thus there is a higher chance of something breaking, especially with cypress upgrades.

Once the feature enabled, logs from these hooks will only appear in console if:

• a command from the hook fails
• hook passes and printLogsToConsole == always
• hook passes and printLogsToConsole ==onFail and includeSuccessfulHookLogs == true

Logging to files

To enable logging to file you must add the following configuration options to the plugin install.

module.exports = (on, config) => {
  // ...
  const options = {
    outputRoot: config.projectRoot + '/logs/',
    outputTarget: {
      'out.txt': 'txt',
      'out.json': 'json',
    }
  };

  require('cypress-terminal-report/src/installLogsPrinter')(on, options);
  // ...
};

The outputTarget needs to be an object where the key is the relative path of the file from outputRoot and the value is the type of format to output.

Supported types: txt, json.

Log specs in separate files

To create log output files per spec file instead of one single file change the key in the outputTarget to the format {directory}|{extension}, where {directory} the root directory where to generate the files and {extension} is the file extension for the log files. The generated output will have the same structure as in the cypress specs root directory.

const path = require('path');

module.exports = (on, config) => {
  const options = {
    outputRoot: config.projectRoot + '/logs/',
    // Used to trim the base path of specs and reduce nesting in the
    // generated output directory.
    specRoot: path.relative(config.fileServerFolder, config.integrationFolder),
    outputTarget: {
      'cypress-logs|json': 'json',
    }
  };
};

Custom output log processor

If you need to output in a custom format you can pass a function instead of a string to the outputTarget value. This function will be called with the list of messages per spec per test. It is called right after one spec finishes, which means on each iteration it will receive for one spec the messages. See for example below.

NOTE: The chunks have to be written in a way that after every write the file is in a valid format. This has to be like this since we cannot detect when cypress runs the last test. This way we also make the process faster because otherwise the more tests would execute the more RAM and processor time it would take to rewrite all the logs to the file.

Inside the function you will have access to the following API:

• this.size - Current char size of the output file.
• this.atChunk - The count of the chunk to be written.
• this.initialContent - The initial content of the file. Defaults to ''. Set this before the first chunk write in order for it to work.
• this.chunkSeparator - Chunk separator string. Defaults to ''. This string will be written between each chunk. If you need a special separator between chunks use this as it is internally handled to properly write and replace the chunks.
• this.writeSpecChunk(specPath, dataString, positionInFile?) - Writes a chunk of data in the output file.

  // ...
  const options = {
    outputTarget: {
      'custom.output': function (messages) {
        // messages= {[specPath: string]: {[testTitle: string]: [type: string, message: string, severity: string][]}

        Object.entries(allMessages).forEach(([spec, tests]) => {
            let dataString = '';
            // .. Process the tests object into desired format ..
            // Insert chunk into file, by default at the end.
            this.writeSpecChunk(spec, dataString);
            // Or before the last two characters.
            this.writeSpecChunk(spec, dataString, -2);
        });
      }
    }
  };
  // ...

See JsonOutputProcessor implementation as a good example demonstrating both conversion of data into string and chunk write position alternation.

Development

Testing

Tests can be found under /test. The primary expectations are run with mocha and these tests in fact start cypress run instances and assert on their output. So that means there is a cypress suite that is used to emulate the usage of the plugin, and a mocha suite to assert on those emulations.

To add tests you need to first add a case to existing cypress spec or create a new one and then add the case as well in the /test/test.js. To run the tests you can use npm test in the test
directory. You should add it.only to the test case you are working on to speed up development.

Release Notes

3.0.1

• Fix issue with cucumber tests not logging properly to nested files. issue
• Fix issue with filterLog and processLog options running too soon on non-final log list. issue

3.0.0

• ! Breaking change in options.collectTestLogs. First parameter (previously called context) changed.
• ! Possibly breaking change: Test names in output files now contain mocha contexts.
• ! Minimum required cypress version increased to 4.10.0.
• ! Removed deprecated printLogs option on support install.
• Added support for logging commands from before all and after all hooks. issue
• Added support for multiple and nested mocha context. In console logs are tabbed according to nesting level of context and in output files context titles are always added. issue
• Added support for option to process logs. issue merge-request by FLevent29
• Added support to disable verbose logging. issue merge-request by FLevent29
• Updated unicode icons for log types on linux.
• Updated cypress to 6.6.x in tests to confirm support.

2.4.0

• Improved logging of xhr with status code, response data in case of failure and duration. issue merge-request by peruukki
• Added console.debug logging support. merge-request by reynoldsdj
• Improve config schema for trimming options to allow number.

2.3.1

• Fixed issue in nested file output for spec file names containing multiple dots. merge-request by rinero-bigpanda
• Fixed issue in nested file output not cleaning up existing files. issue
• Update to cypress 6.0.0 in tests and fix expectations.

2.3.0

• Added support for custom log collector function on both nodejs and browser sides. issue merge-request by peruukki
• Improved cy.request logging when log set to false and when there are network errors. merge-request by bjowes

2.2.0

• Added support for logging each spec to its own file. issue

2.1.0

• ! Separated option printLogs to printLogsToConsole and printLogsToFile. printLogs won't work anymore and will print a warning in the cypress logs. Read documentation on how to upgrade. issue merge-request by FLevent29
• Typescript typings support added. issue merge-request by bengry

2.0.0

• Removed deprecated exports from index.js. If you were still using require from index.js please see installation for updating.
• Added JSON schema validation for options to prevent invalid options and assumptions. issue
• Fixed issue where output to file would insert at incorrect position for JSON when ran from GUI.
• Reworked the file output processing code and thus the API changed as well. Custom output processors will have to be updated to current API when upgrading to this version. Check readme section.
• Added printing to terminal of time spent in milliseconds for output files to be written.
• Improved Error instanceof checking for console log arguments printing. issue
• Update cypress to 5.0.0 in tests to confirm compatibility.

1.4.2

• Fixed issue with compact logs breaking after each hook with message undefined is not iterable. issue
• Update cypress to 4.11.0 in tests to confirm compatibility.

1.4.1

• Added log to terminal of the list of generated output files. merge-request by @bjowes
• Fixed line endings for output on windows. merge-request by @bjowes
• Fixed incorrect readme with inverse installation requires for plugin and support. merge-request by @zentby

1.4.0

• Added new feature to compact output of logs, see here. issue
• Fixed incorrect severity on cons:error and cons:warn.
• Fixed compatibility with cypress 4.8. issue-1 issue-2 issue-3
• Fixed issue with webpack compatibility caused by native includes getting in compilation files. For this please revise the installation documentation and change the requires for the install of this plugin. Deprecated require by index. issue
• Fixed issue with logsChainId not being reset and causing test failures and potentially live failures with error 'Cannot set property '2' of undefined'. issue

1.3.1

• Added creation of output path for outputTarget files if directory does not exist.
• Fixed issue with ctrAfter task not being registered when outputTarget not configured. issue

1.3.0

• Added support for logging to file, with builtin support for json and text and possible custom processor. issue
• Added support for logging XHR request body and also headers for requests and responses. issue
• Reformatted the log message for route and request commands.
• Replace all tab characters with spaces on console log.

1.2.1

• Fixed issue with incorrect command being marked as failing when there are additional logs after the actual failing one. issue
• Fixed issue where console would receive undefined and the plugin would break: split on undefined. issue
• Bumping default trim lengths for cy:command and cons:* log types.
• Improvements on logging objects from console.
• Fix incorrect severity calculation for cy:route.
• Fix yellow output on powershell.
• Fix windows console icons with different set. issue
• Update cypress version for testing to 4.3.0.
• Set peer version of cypress to >=3.8.1. issue

1.2.0

• Fixed issue with cy.request accepting parameters in multiple formats and the plugin not recognizing this. merge-request by @andrew-blomquist-6
• Improved browser console logs for Error and other objects. issue-1 issue-2
• Added support for filtering logs. See collectTypes and filterLog options for the support install. from issue.
• Removed option printConsoleInfo in favor of above. Also now the console.log and info are by default enabled.

1.1.0

• Added notice for logs not appearing in dashboard. from issue
• Added support for logging console.info and console.log. in issue
• Added better logging of cy.requests. in issue by @zhex900

1.0.0

• Added tests and CI to repository.
• Added support for showing logs even for successful tests. in issue by @zhex900
• Fixed issue with incorrectly labeled failed commands. in issue by @zhex900
• Fixed issue with logs from cy.route breaking tests on XHR API type of requests. merge-request by @zhex900