fix: log multiple arguments passed in the click method

[Manuel-Suarez-Abascal]

• Closes 485

Additional details

N/A

Steps to test

To reproduce the current behavior, the issue provides the following test code:

it('test', () => {
  cy.visit('https://example.cypress.io/commands/actions')
  cy.get('#action-canvas').click('topRight')                // command log shows '{position: topRight}'
  cy.get('#action-canvas').click('topRight', { force: true }) // command log shows '{force: true, position: topRight}'
})

How has the user experience changed?

Now both the arguments & options get logged in Cypress's Test Runner. Check the image below for more context:

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]

5 failed and 34 flaky tests on run #45270 ↗︎

5

26904

1281

0

34

Details:

fix: log multiple arguments passed in the click method
Project: cypress	Commit: 37ccc2b19f
Status: Failed	Duration: 19:38 💡
Started: Apr 4, 2023 8:29 PM	Ended: Apr 4, 2023 8:49 PM

  cypress/e2e/commands/actions/click.cy.js • 1 failed test • 5x-driver-electron

View Output Video

Test		Artifacts
... > can specify x and/or y to be 0		Output Video

  cypress/e2e/commands/actions/click.cy.js • 1 failed test • 5x-driver-firefox

View Output Video

Test		Artifacts
... > can specify x and/or y to be 0		Output

  cypress/e2e/commands/actions/click.cy.js • 1 failed test • 5x-driver-chrome:beta

View Output Video

Test		Artifacts
... > can specify x and/or y to be 0		Output Video

  cypress/e2e/commands/actions/click.cy.js • 1 failed test • 5x-driver-chrome

View Output Video

Test		Artifacts
... > can specify x and/or y to be 0		Output Video

  cypress/e2e/commands/actions/click.cy.js • 1 failed test • 5x-driver-webkit

View Output Video

Test		Artifacts
... > can specify x and/or y to be 0		Output Video

  create-from-component.cy.ts • 2 flaky tests • app-e2e

View Output Video

Test		Artifacts
... > runs generated spec		Output Screenshots Video
... > runs generated spec		Output Screenshots Video

  runner/reporter.command_errors.cy.ts • 1 flaky test • app-e2e

View Output Video

Test		Artifacts
errors ui > cy.readFile		Output Screenshots Video

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

View Output Video

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

  cypress-in-cypress-component.cy.ts • 1 flaky test • app-e2e

View Output Video

Test		Artifacts
Cypress In Cypress CT > default config > redirects to the specs list with error if a spec is not found		Output Screenshots Video

  cypress-origin-communicator.cy.ts • 1 flaky test • app-e2e

View Output Video

Test		Artifacts
Cypress In Cypress Origin Communicator > cy.origin passivity with app interactions > passes upon test reload mid test execution		Output Screenshots Video

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

_{This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.}

[emilyrohrbough]

@Manuel-Suarez-Abascal Thank you so much for taking on this issue! We will need to add some test coverage for this to get across the line.