This PR was created in participation of an internal company bug hunt. The goals for this bug hunt are:
Setting up Cypress 10 end-to-end in a new project
Migrating an existing end-to-end project on an older Cypress version to Cypress 10
Writing and running end-to-end tests in Cypress 10 open mode and run mode
Working with Cypress 10 in different operating systems, containers, and environments
Recording to the Cypress Dashboard with Cypress 10
Using the Cypress 10 documentation to help with any of the above
Not all of these goals will be met by me alone; this is a company-wide effort. My focus is particularly with item 1, and nuances within it:
[x] Can I set up a "fresh" project with Cypress V10?
Yes, but encountered issue where test type options didn't render; relaunching fixed the issue - tracked in UNIFY-1443
[ ] Can I set up mock infrastructure as easy as before? No need at the moment; HTML is generated at build time, so the data has already been queried by the time the tests are run
In other words, the data is already there - this means:
Nothing to mock
Tests should be either "high level" (and ignore content completely), or built around specific data that's not expected to change
[x] Are there issues with adding, removing or otherwise maintaining custom Cypress commands? - Nope! Works easily
I will add items to this list as I think of them - note that I will likely not reach all items within the 4 hour testing window. I'll keep digging into this since my project actually needs this, anyway
Notes
Friction with file types - it's clear you need to configure the spec pattern if you intend to use something other than the default (cypress/e2e/**/*.cy.{js,jsx,ts,tsx})
The in-app assistance brings you to the correct file and points to the correct docs, but it's not exactly clear what needs to be added/modified in the file from looking at the docs
Old docs say to use an integrations folder - this is no longer the case
e2e directory should hold end to end tests
I assume there is a components equivalent, but that's not live yet, so I'm not testing it yet
This PR was created in participation of an internal company bug hunt. The goals for this bug hunt are:
Not all of these goals will be met by me alone; this is a company-wide effort. My focus is particularly with item 1, and nuances within it:
Can I set up mock infrastructure as easy as before?No need at the moment; HTML is generated at build time, so the data has already been queried by the time the tests are runI will add items to this list as I think of them - note that I will likely not reach all items within the 4 hour testing window. I'll keep digging into this since my project actually needs this, anyway
Notes
cypress/e2e/**/*.cy.{js,jsx,ts,tsx})integrationsfolder - this is no longer the casee2edirectory should hold end to end testscomponentsequivalent, but that's not live yet, so I'm not testing it yet