Skip to content

chore: update cross origin command error #24891

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

Merged
merged 4 commits into from
Dec 2, 2022

Conversation

AtofStryker
Copy link
Contributor

@AtofStryker AtofStryker commented Nov 29, 2022

  • Closes N/A

User facing changelog

Additional details

Adds explainer to cross_origin_command error to point users to Error Messages in v12 docs (Link needs to be added). see cypress-io/cypress-documentation#4880
Screen Shot 2022-11-29 at 5 55 44 PM

Steps to test

How has the user experience changed?

PR Tasks

  • Have tests been added/updated?
  • Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
  • Has a PR for user-facing changes been opened in cypress-documentation?
  • Have API changes been updated in the type definitions?

@cypress-bot
Copy link
Contributor

cypress-bot bot commented Nov 29, 2022

Thanks for taking the time to open a PR!

@AtofStryker AtofStryker changed the title Chore/update cross origin command error chore: update cross origin command error Nov 29, 2022
\` <commands targeting ${autOrigin} go here>\`
\`})\`
`,
docsUrl: 'https://on.cypress.io/cy-visit-succeeded-but-commands-are-timing-out-because-you-visited-a-different-origin-domain-without-using-cy-origin',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

whoa....this feels crazy verbose. Any way we could shorten?

https://on.cypress.io/visit-failed-wrong-origin',

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can I just have no idea how these mappings are generated or linked. Thats just the header link in cypress-io/cypress-documentation#4880

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to create a on link in the services repo with the docs reference

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hows https://on.cypress.io/cy-visit-succeeded-but-commands-fail?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AtofStryker AtofStryker marked this pull request as ready for review November 29, 2022 22:51
@cypress
Copy link

cypress bot commented Nov 29, 2022



Test summary

21730 0 1716 0Flakiness 3


Run details

Project cypress
Status Passed
Commit 6986694
Started Dec 2, 2022 2:41 PM
Ended Dec 2, 2022 2:58 PM
Duration 17:33 💡
OS Linux Debian -
Browser Multiple

View run in Cypress Dashboard ➡️


Flakiness

project-setup.cy.ts Flakiness
1 ... > shows the configuration setup page when selecting e2e tests
cypress-in-cypress-run-mode.cy.ts Flakiness
1 Cypress In Cypress - run mode > e2e run mode spec runner header is correct
cypress-origin-communicator.cy.ts Flakiness
1 Cypress In Cypress Origin Communicator > cy.origin passivity with app interactions > passes upon test reload mid test execution

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

@AtofStryker AtofStryker force-pushed the chore/update-cross-origin-command-error branch from 082058e to 12d5ce1 Compare December 1, 2022 21:14
@mjhenkes mjhenkes merged commit 4c669b3 into release/12.0.0 Dec 2, 2022
@mjhenkes mjhenkes deleted the chore/update-cross-origin-command-error branch December 2, 2022 15:06
@AtofStryker
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants