-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Should not truncate full url during cy.request() in stdout #3145
Comments
Hi @cmcnicholas, I want to be sure about where you are seeing this data. When you review this output, you are on the Cypress Dashboard webpage? So, visiting a url like: |
Yes that is correct @jennifer-shehane |
Thanks for the reply. The truncating appears to be happening within the CLI, so the full url is never being fully printed in the output that is later printed in the Dashboard. Doing
The code for this url to print in the error message is
So, I would recommend removing this truncation, if we have to set a limit, it seems that the standard recommended cutoff for urls is 2000 characters. |
The code for this is done in cypress-io/cypress#5150, but has yet to be released. |
Released in |
Is this a Feature or Bug?
I believe this to be a bug with Cypress dashboard where truncation of the output makes debugging issues via the dashboard or CI very difficult for developers. It is useful for instance to see body and url parameters when using something like
cy.request
however the output on failure is formatted in a way which inhibits the ability to debug issues.Current behavior:
the output in the cypress dashboard for a 404 (any sufficiently large output will do) looks like
see that the body and url are being truncated in this final block of the log. For small payloads it's fine, but when payloads become larger (or other cy methods that produce longer lines) the truncation makes the output almost useless. This is more of a problem when the errors are only produced on the CI server.
Desired behavior:
I would like some control over the output here, several options:
Steps to reproduce: (app code and test code)
Simply perform a
cy.request
with a sufficiently large url or body e.g.Versions
Cypress: 3.1.3
I don't believe the browser to be an issue in this specific issue.
The text was updated successfully, but these errors were encountered: