-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
chore: move e2e tests into component source dirs #16117
Conversation
Thanks @devversion for helping with the pile of CI failures! |
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.
LGTM
Awesome! the macro for the e2e tests really reduces the duplication 👍 |
* chore: move e2e tests into component source dirs * move utils in e2e/ to src/e2e-app/ * move e2e tests to the component's src dir * update owners and uses of gulp/bazel * fix some targets I missed when renaming * move e2e test utils under @angular/cdk/testing * fix lint
* chore: move e2e tests into component source dirs * move utils in e2e/ to src/e2e-app/ * move e2e tests to the component's src dir * update owners and uses of gulp/bazel * fix some targets I missed when renaming * move e2e test utils under @angular/cdk/testing * fix lint
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
I'm naming e2e test files
*.e2e.spec.ts
to differentiate them from unit tests, and adding thee2e
tag to e2e blaze targets to differentiate those.