misc: update command message to truncate command info at 100 lines instead of 50

[jennifer-shehane]

• Closes Do not shorten command message text with ellipsis #29023

Additional details

We currently truncate the command message in the Cypress command log to 50 lines. The main concern around truncating that I ran into is that full URLs are not visible, the trail off with ellipsis. This hasn't been a big problem in cypress open because you can just click on the command and see the full URL in devtools. However, since we use the reporter css for Test Replay, this URL is not visible in Test Replay. You'd have to remove the css from devTools to see it. This change will need to be ported over to Test Replay.

This behavior of truncating the command messages has a long history and there's been a series of states when it comes to truncating the command messages in the Cypress command log. I was trying to track down the true intention behind what we want as a product. In the end, I think it's best to make the truncation slightly longer.

• 6 years ago Chris opened a PR to no longer truncate URLs in the command log, this was a welcome change. Don’t truncate xhr urls in command log #2004
• In Cypress 3.8.2 a contributor opened a PR to truncate all Cypress log messages to 50 lines instead of 1 as it was before: Truncate cy.log() in Command Log to 50 lines instead of 1 #5630 There was a discussion there where I noted: "The purpose of restriction would be to prevent the reporter from printing a gigantic log, like if someone accidentally printed a large Object, that may lock up the browser during rendering. Something more than this amount of characters wouldn't even be visible in a single frame of the test runner for review."
• In Cypress 10.0.0, there was a change to command log styling where the message truncation was lost. feat(Unification): Update Command Group UI #20465
• In Cypress 10.10.0, a contributor 'fixed' the command message truncation that had been lost. fix: clamp command output to 50 lines #24089

One thing of note is that it's generally accepted to keep URLs below 2000 chars, so that may be a consideration for this.

Steps to test

How has the user experience changed?

Before

After

PR Tasks

• Have tests been added/updated?
• Has a PR for user-facing changes been opened in cypress-documentation?
• Have API changes been updated in the type definitions?

[cypress]

10 flaky tests on run #54449 ↗︎

0

29111

1324

0

10

Details:

Merge branch 'develop' into untruncate-command-message
Project: cypress	Commit: 347e65c14d
Status: Passed	Duration: 19:37 💡
Started: Mar 11, 2024 2:00 PM	Ended: Mar 11, 2024 2:19 PM

  commands/querying/querying.cy.js • 1 flaky test • 5x-driver-electron

View Output

Test		Artifacts
... > throws after timing out after a .wait() alias reference		Test Replay

  commands/waiting.cy.js • 1 flaky test • 5x-driver-electron

View Output

Test		Artifacts
... > waits for requestTimeout and responseTimeout override		Test Replay

  e2e/origin/navigation.cy.ts • 1 flaky test • 5x-driver-electron

View Output

Test		Artifacts
... > establishes foobar spec bridge		Test Replay

  specs_list_latest_runs.cy.ts • 1 flaky test • app-e2e

View Output

Test		Artifacts
App/Cloud Integration - Latest runs and Average duration > when no runs are recorded > shows placeholders for all visible specs		Test Replay Screenshots

  commands/net_stubbing.cy.ts • 1 flaky test • 5x-driver-chrome:beta

View Output

Test		Artifacts
network stubbing > waiting and aliasing > yields the expected interception when two requests are raced		Test Replay

The first 5 flaky specs are shown, see all 9 specs in Cypress Cloud.

Review all test suite changes for PR #29032 ↗︎

[cypress-bot]

Released in 13.7.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v13.7.0, please open a new issue.