-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Prepare Studio Feature branch for review #23461
Comments
This is blocked until all other things in #23230 are completed. |
TestingThere are quite a number of workflows we need to consider to have feature parity. I'll document those here. I'll use Cypress 9 to document the stories, since that's the parity we are aiming for. 1. Basic "happy" path
You should be prompted to create a test with Cypress Studio:
This is what was generated for mine: /* ==== Test Created with Cypress Studio ==== */
it('My awesome test', function() {
/* ==== Generated with Cypress Studio ==== */
cy.visit('https://lmiller1990.github.io');
cy.get('.center').click();
cy.get('.job-title > strong').click();
/* ==== End Cypress Studio ==== */
});
/* ==== Test Created with Cypress Studio ==== */
it('jj', function() {
/* ==== Generated with Cypress Studio ==== */
cy.visit('https://lmiller1990.github.io/');
cy.get(':nth-child(3) > :nth-child(3)').click();
/* ==== End Cypress Studio ==== */
/* ==== Generated with Cypress Studio ==== */
cy.get('.resume > :nth-child(5)').click();
cy.get('.resume > :nth-child(5)').click();
cy.get('.resume > :nth-child(5)').click();
/* ==== End Cypress Studio ==== */
}); |
The code for this is done in cypress-io/cypress#23544, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Part of #23230
Studio support is in feature branch feat/studio-cypress-10
Once all the other Studio stories are complete, we need to do a final pass on the feature branch, test it all out, and prepare it for a thorough review and QA.
AC:
The text was updated successfully, but these errors were encountered: