-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
refactor: cleanup for ported vue2 module #21062
refactor: cleanup for ported vue2 module #21062
Conversation
Thanks for taking the time to open a PR!
|
…press-io/cypress into tgriesser/cleanup/UNIFY-1253-npm-vue2 * 'tgriesser/cleanup/UNIFY-1253-npm-vue2' of github.com:cypress-io/cypress: update test truncate confusing vue loader message
@@ -1,9 +0,0 @@ | |||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we sure we don't want to retain at least some tests over this module? I agree it makes sense not to duplicate everything (especially the examples), but deleting the entire test setup feels a bit much. This is still going to be published as a separate package on NPM that we have to maintain, and I'm not sure we have test coverage of it other than the deleted files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should port some of these tests in general to system-tests. This Cypress project currently isn't even setup properly at all for the new architecture (it's still using the legacy plugin api). We're doing that as part of the other tickets for each of the dev servers
User facing changelog
n/a
Additional details
cypress.json
) & we have decided all tests should be run in thesystem-tests
foldercypress-vue
->cypress-vue2
for the bundled files for clarity: ec2a259How has the user experience changed?
PR Tasks
cypress-documentation
?type definitions
?cypress.schema.json
?