Hi friends! PMM team at Cypress have a quick request... they are collecting feedback from the community on cross-origin testing with Cypress and test isolation. We’re looking to learn more about: - Use case(s) for cross-origin testing and our recently released cy.origin command - Use case(s) for sharing state between tests and cy.session - Points of confusion for: Implementing cy.origin and/or cy.session; Converting a test suite when enabling the commands; UI for how the commands are shown when writing tests; Existing documentation on the commands Please (please, please!) take our brief survey: https://forms.gle/NTWU6mjznJcQwfen9 Your feedback is critical to ensuring our product meets the needs of our customers. When you complete the survey, you can opt-in to win your very own Cypress t-shirt 🎁

It would be very neat if the team created open recipe repos like this one : https://github.com/muratkeremozcan/auth0-cypress It's important that the secrets are shared, so that whoever is reproducing doesn't have to wrestle auth provider specific things, which aren't related to the feature. You have Auth0 covered. Would be even neater if the recipe later showed the updated programmatic login in contrast

That contribution basically handles the most difficult obstacle a new team has to figure out; logging in. It would accelerate Cypress adoption by a factor.

Fromt Filip's Discord server, I always thought that storing some small JSON with each test and then visualizing them across runs would be a killer Dashboard feature

yea there are a poor man's versions of that console with a task 😂 No joke, we are actually using that to cross reference issues with DataDog

Hey, I'm evaluating https://dashboard.cypress.io/ and I think it would be useful to add comment on a test run and/or on a (failed) test. Basically, I want to explain why a particular test or test run has an unexpected result. Creating an issue on JIRA feels a bit too much when I just want to annotate/comment something. Anyway thanks for this great product!

Cypress could have a way to save all the data of a failing test to a file, including all the requests and response's data, user input and their exact timings, in order to be able to replicate a bug that rarely happens or happens in odd situations.

Then have another way to run that file and it should fail the same way, provided the website being tested didn't change, EDIT: nevermind, the website response should be stored in the file.

Then you could try editing the timings and/or some other stuff and/or compare the details with a test that passed and figure out what variable caused the issue.

Hi there, currently I upgrade Cypress to 9.6.1 to test cy.origin, but I got the following error for the custom reporter.

which custom reporter? is there a reproducible repo? If a developer took on this issue, what information do they have to move forward with? Should they, since it's a custom reporter?

FYI": As someone with not much coding knowledge I am going to miss Cypress studio 🙂 Saw the alternative but will miss the easy assertions etc

I’ve answered this in another channel. Please don’t post to multiple channels asking for help. It just creates noise

Hi! First, thanks for letting me join this community. I am trying to run accessibility tests on every page. I want to automate this by reading the xml of that particular website and than running cy.injectAxe() and cy.checkA11y() to check every page. I found some code which could read the xml already, the problem I am having is.. where do I put the accessibility test after each page is loaded. I am sadly quite technically limited (still learning a lot, I was a photographer which switched to QA last year sep). This is the code which checks accessibility for one page. --- describe('Homepage has no axe issues', () => { beforeEach(() => { cy.visit('https://www.ibsbelgium.org/') cy.get('.elementor-element-577dacd2 > .elementor-column-wrap > .elementor-widget-wrap > .elementor-element > .elementor-widget-container > .elementor-button-wrapper > .elementor-button-link') .click() cy.injectAxe() }) it('Has no detectable a11y violations on load', () => { cy.checkA11y() }) }) --- This the code which reads an xml and than iterates on all links within that XML --- describe('Sitemap', () => { let urls = [] before(async () => { const response = await cy.request('https://www.ibsbelgium.org/post-sitemap.xml') urls = Cypress.$(response.body) .find('loc') .toArray() .map(el => el.innerText) }) it('should succesfully load each url in the sitemap', () => { urls.forEach(cy.visit) }) }) ---

it's not really a cypress feature, but a plugin usually it's as simple as

it('foo', () => {
    // do some stuff

    cy.injectAxe()

    cy.checkA11y(null, {
      includedImpacts: ['minor'],
    })
  })

Hi Murat, indeed. This is what works on my end too for one page. But I need to to iterate on all of my url's which gets extracted out of an XML. I am not succeeding in that.

I think I get it if you had 2 urls, would it be something like this?

it('foo', () => {
    cy.visit('/1')

    cy.injectAxe()

    cy.checkA11y(null, {
      includedImpacts: ['minor'],
    })
  })

  it('foo2', () => {
    cy.visit('/2')

    cy.injectAxe()

    cy.checkA11y(null, {
      includedImpacts: ['minor'],
    })
  })

try this https://github.com/bahmutov/cypress-each an example is here https://dev.to/muratkeremozcan/crud-api-testing-a-deployed-service-with-cypress-using-cy-api-spok-cypress-data-session-cypress-each-4mlg#data-driven-tests-with-cypress-each

you're going to have to wrestle the "extracting the xml" part

On the changelog section of cy v10, the link to current support for frameworks and bundlers is leading to a 404. Just a heads up!

https://docs.cypress.io/guides/overview/choosing-testing-type 404

@purple-shampoo-89307 here's the blog with updated links: https://cypress.io/blog/2022/06/01/cypress-10-release/

On the changelog section of cy v10 the

I have a issue in the head / Stats, it is esthetics issue

Has the button to run all specs at once been removed in this new version?

Yes https://docs.cypress.io/guides/references/changelog#10-0-0 4th to last bullet under breaking changes. I'm a little confused why this would be removed as well without some sort of replacement, even if the most common scenario is only running a single spec. I guess there was some technical difficulty supporting it on their new platform? Link to leave feedback at least...

Hey @future-gold-77198 & @better-river-75183 yes it has been removed, mainly to improve parity with

cypress run

. Sorry if the feedback link is not discoverable, but we are taking feedback on this discussion https://github.com/cypress-io/cypress/discussions/21628 and would love to hear your input!

I have a issue in the head Stats it is

Hi everyone. The firefox browser installed from the Microsoft store (MSIX package) could not be selected as the preferred browser. Browser version: 100.2 - OS: Windows 11

Anyone having trouble with the migration? I seem to be getting stuck with the configuration for component testing.