You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run my tests in headless mode, I do not receive any output in my console log, though report is generated.
I have a sample spec with 1 failing test. I launch it using the following command: as-a staging cypress run, where 'staging' is a user in staging env, or CYPRESS_BASE_URL=... cypress run.
In both cases I can see no message 'Test failed, details in $1' in my output. Instead, a file 'failed-exec.json' is generated in the project root folder. It contains the following data:
"stdout": "",
"stderr": "/bin/bash: ./on-failed.sh: No such file or directory",
"code": 127
}
A report file, 'failed-${testname}.json' appears next to it.
I have require('cypress-failed-log'); in my support/index.js and NPM script failed-test in package.json. The cypress-failed-log package is listed under devDependencies in package.json.
Cypress version: 2.1.0
cypress-failed-log: 2.0.0
My tests are running under macOS.
The text was updated successfully, but these errors were encountered:
When I run my tests in headless mode, I do not receive any output in my console log, though report is generated.
I have a sample spec with 1 failing test. I launch it using the following command:
as-a staging cypress run
, where 'staging' is a user in staging env, orCYPRESS_BASE_URL=... cypress run
.In both cases I can see no message 'Test failed, details in $1' in my output. Instead, a file 'failed-exec.json' is generated in the project root folder. It contains the following data:
A report file, 'failed-${testname}.json' appears next to it.
I have
require('cypress-failed-log');
in my support/index.js and NPM script failed-test in package.json. The cypress-failed-log package is listed under devDependencies in package.json.Cypress version: 2.1.0
cypress-failed-log: 2.0.0
My tests are running under macOS.
The text was updated successfully, but these errors were encountered: