-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
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_NO_COMMAND_LOG=1 leaves faulty empty space #21271
Comments
Thanks for opening an issue. I was able to reproduce on 9.6.0 and 8.0.0. It looks like a regression occurred sometime between v7.0.0 (verified it works) and v8.0.0 (verified it does not work). |
I tested this out in v10.0.2 and realized we don't yet have support for this environment variable in v10+. Here is a related issue for implementing that support: #21721 We should ensure that the spacing issue called out here is taken care of as part of that work. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Current behavior
Hello, currently when running
CYPRESS_NO_COMMAND_LOG=1 npm run cy:open
and opening any test - there is some space left where Test Runner Command Log should be. Probably because of reporterProbably empty space is left there because
<div class="reporter-wrap" style="left: 0px;"></div>
is not deleted. If to delete it and resize the Test Runner window - empty space will disappear.vid.mov
Desired behavior
There is no space left where Test Runner Command Log should be when using

CYPRESS_NO_COMMAND_LOG=1
environment variable:Test code to reproduce
Should be reproducible anywhere, I tested it on the fresh 9.6.0 Cypress project with getting started examples.
Cypress Version
8.7.0, 9.6.0
The text was updated successfully, but these errors were encountered: