Cypress pipe console.log and command log to output

As of Cypress 3.0.0, you can use cy.task() to access node directly and output to the node console. From the docs:

// in test cy.task('log', 'This will be output to the terminal') 

// in plugins file on('task', { log (message) { console.log(message) return null } }) 

See here for more info.

I don't know of a way to mirror the Cypress logs to the console directly, but this is at least a workable alternative.

Setting the ELECTRON_ENABLE_LOGGING environment variable to 1 will cause all Chrome internal logging to be printed to the console.

ELECTRON_ENABLE_LOGGING=1 npx cypress run 

ELECTRON_ENABLE_LOGGING

Prints Chrome's internal logging to the console.

With this enabled, in addition to capturing any existing logging, this will also allow you to manually log within a test using console.log:

console.log('Response JSON: ' + json) 

FYI:

Cypress community is going to provide native support so that we don't have to do any workarounds to print the logs on non-GUI(headless) CLI.

Ongoing issue: https://github.com/cypress-io/cypress/issues/448 includes reference to 3 existing workarounds https://github.com/cypress-io/cypress/issues/448#issuecomment-613236352

Expanding on @Joshua-wade's answer, you can overwrite cy.log to redirect all calls to it to the log task. Just as the following:

Cypress.Commands.overwrite('log', (subject, message) => cy.task('log', message));

Note: there's a small drawback to this: when you run the test using the Test Runner, instead of seeing LOG my message in the command log, you'll see TASK log, my message. But IMHO it's negligible.

// cypress.config.js const { defineConfig } = require("cypress"); module.exports = defineConfig({ projectId: "cnpkrh", e2e: { setupNodeEvents(on, config) { on('task', { log(message) { console.log(message); return null; }, }); }, }, }); // cypress/e2e/spec.cy.js cy.task('log', 'This will be output to the terminal') 

Disclaimer: I am the plugin author

You can capture Cypress CI GUI commands in headless mode, together with all the network requests, browser console messages and DOM tree changes using this free open-source plugin: https://github.com/currents-dev/cypress-debugger

As an alternative, you can also use a set of other well-known plugins:

• https://github.com/archfz/cypress-terminal-report to print the browser log messages and cypress steps to terminal
• https://github.com/NeuraLegion/cypress-har-generator to capture network requests as a file

I agree with Araon's approach using overwrite on the log function. Another approach, if you want to keep cy.log the default behavior, would be create a custom command. Doc here

Example: Cypress.Commands.add("printLog", (message) => { cy.task("log", {message}); })

This way you can call function printLog vs cy.task("log", {message});

You could use the very handy cypress-terminal-report plugin.

This provides verbose output on failure including:

• Commands given
• Network calls made along with their responses before and after those commands
• Any console logs or error output

For me, it's a must-have tool to improve Cypress E2E.