We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With the release of Angular 16 just around the corner, we need to validate that it does not break Angular Component Testing.
signals
We want to make sure we are providing CT support for Angular users as close to release of 16 as possible.
No response
The text was updated successfully, but these errors were encountered:
This is ready for review but the Angular 16 release got pushed back to April/May so marking as blocked until we get closer to release
Sorry, something went wrong.
Released in 12.11.0.
12.11.0
This comment thread has been locked. If you are still experiencing this issue after upgrading to Cypress v12.11.0, please open a new issue.
jordanpowell88
Successfully merging a pull request may close this issue.
What would you like?
With the release of Angular 16 just around the corner, we need to validate that it does not break Angular Component Testing.
signals
so we need to validate it works as expected and provide examples in our system tests for examples with signals.Why is this needed?
We want to make sure we are providing CT support for Angular users as close to release of 16 as possible.
Other
No response
The text was updated successfully, but these errors were encountered: