We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cypress:server:specs
Guides
The debug log source cypress:server:specs, referred to in multiple examples, does not produce any debug logs.
Core Concepts > Writing and Organizing Tests > Troubleshooting advises:
If Cypress does not find the spec files for some reason, you can troubleshoot its logic by opening or running Cypress with debug logs enabled:
DEBUG=cypress:server:specs npx cypress open ## or DEBUG=cypress:server:specs npx cypress run
Neither of these commands produces debug logs using the current version of Cypress 13.14.2.
13.14.2
Locations referring to non-working cypress:server:specs are:
spec
Location referring to partially working cypress:server:specs is:
9.x
The text was updated successfully, but these errors were encountered:
10.0.0
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Subject
Guides
Description
The debug log source
cypress:server:specs
, referred to in multiple examples, does not produce any debug logs.Core Concepts > Writing and Organizing Tests > Troubleshooting advises:
If Cypress does not find the spec files for some reason, you can troubleshoot its logic by opening or running Cypress with
debug logs enabled:
DEBUG=cypress:server:specs npx cypress open ## or DEBUG=cypress:server:specs npx cypress run
Neither of these commands produces debug logs using the current version of Cypress
13.14.2
.Locations
Locations referring to non-working
cypress:server:specs
are:spec
parameterLocation referring to partially working
cypress:server:specs
is:spec
parameter. This works correctly on Cypress9.x
on Windows (probably also on macOS), but not on Linux. There was a general issue with selective logging on Linux which was not fixed until [email protected].The text was updated successfully, but these errors were encountered: