misc: write command durations to a csv file

[cacieprins]

• Closes

Additional details

If CYPRESS_INTERNAL_COMMAND_PERFORMANCE_LOGGING is enabled, Cypress will:

• Create a new csv file at ./cypress/logs/performance.log, or $CYPRESS_INTERNAL_PERFORMANCE_LOG_FILE_PATH/performance.log if CYPRESS_INTERNAL_PERFORMANCE_LOG_FILE_PATH is set. This file is overwritten each time Cypress starts.
• Append performance data to this file for every command:
  • startTime - when the Command Queue began executing the command
  • duration - How long the command took to execute
  • name - The name of the command
  • numElements - the number of elements associated with the command (for queries, this is the number of elements that match the query)
  • runnableTitle - the title of the runnable that enqueued the command
  • spec - the filename of the spec that included the runnable

Steps to test

How has the user experience changed?

PR Tasks

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

---

Note

Adds env-gated logging of each command’s execution timing to a CSV file and wires it through driver → automation (CDP/BiDi) → server.

• Performance logging (opt-in via CYPRESS_INTERNAL_COMMAND_PERFORMANCE_LOGGING):
  • Driver: make runCommand async, measure startTime/duration, capture numElements, and emit Cypress.automation('log:command:performance', ...) from command_queue.ts.
  • Server: add record_performance_entry to append CSV rows to ./cypress/logs/performance.log (path override via CYPRESS_INTERNAL_PERFORMANCE_LOG_FILE_PATH) and initialize file on mode start (modes/index.ts).
  • Automation:
    • Wire new command log:command:performance through generic automation, plus CDP (cdp_automation.ts) and BiDi (bidi_automation.ts) handlers.
    • Extend types with CommandPerformanceEntry and new automation command in @packages/types.
  • Changelog: document the new benchmarking capability and default log location.

^{Written by Cursor Bugbot for commit d80bf84. This will update automatically on new commits. Configure here.}

[jennifer-shehane]

@cacieprins If this is meant to be a user facing feature - I would not prefix this with CYPRESS_INTERNAL as that is used for truly internal env vars that users should never set.

[cacieprins]

I think if it's something we want user-facing, it should be a config entry - but that's out of scope for this, I think. This is to prep for benchmarking visibility approaches

[cypress]

cypress    Run #67520

Run Properties:   Failed #67520  •  7084eafc4a: refactor to performance marks, clean up telemetry on the client, make log writer...

Project	cypress
Branch Review	csv-benchmark
Run status	Failed #67520
Run duration	19m 34s
Commit	7084eafc4a: refactor to performance marks, clean up telemetry on the client, make log writer...
Committer	Cacie Prins
View all properties for this run ↗︎

---

Test results
Failures	6
Flaky	11
Pending	1098
Skipped	4
Passing	26691
View all changes introduced in this branch ↗︎

---

Warning

Partial Report: The results for the Application Quality reports may be incomplete.

UI Coverage  45.76%
Untested elements	187
Tested elements	162

Accessibility  98%
Failed rules	4 critical   8 serious   2 moderate   2 minor
Failed elements	101

---

Tests for review

  commands/location.cy.js • 1 failed test • 5x-driver-electron

View Output

Test		Artifacts
src/cy/commands/location > #location > eventually returns a given key		Test Replay

  commands/location.cy.js • 1 failed test • 5x-driver-chrome:beta

View Output

Test		Artifacts
src/cy/commands/location > #location > eventually returns a given key		Test Replay

  commands/location.cy.js • 1 failed test • 5x-driver-firefox

View Output

Test		Artifacts
src/cy/commands/location > #location > eventually returns a given key		</td> </tr></table>   commands/location.cy.js • 1 failed test • 5x-driver-chrome View Output Test Artifacts src/cy/commands/location > #location > eventually returns a given key Test Replay   studio/studio-ui.cy.ts • 1 failed test • app-e2e View Output Test Artifacts Cypress Studio - UI and Panel Management > studio AI is marked as coming soon Test Replay Screenshots The first 5 failed specs are shown, see all 6 specs in Cypress Cloud.   commands/files.cy.js • 1 flaky test • 5x-driver-electron View Output Test Artifacts ... > throws when there is an error reading the file Test Replay   issues/28527.cy.ts • 1 flaky test • 5x-driver-electron View Output Test Artifacts issue 28527 > fails and then retries and verifies about:blank is not displayed Test Replay Screenshots   commands/waiting.cy.js • 1 flaky test • 5x-driver-chrome:beta View Output Test Artifacts ... > errors > throws when waiting for 2nd response to route Test Replay   issues/28527.cy.ts • 1 flaky test • 5x-driver-chrome:beta View Output Test Artifacts issue 28527 > fails and then retries and verifies about:blank is not displayed Test Replay Screenshots   commands/net_stubbing.cy.ts • 1 flaky test • 5x-driver-firefox View Output Test Artifacts ... > stops waiting when an xhr request is canceled </td> </tr></table> The first 5 flaky specs are shown, see all 11 specs in Cypress Cloud.