Skip to content

test(core): fix expectations that accidentally used incorrect matchers#55294

Closed
leonsenft wants to merge 1 commit intoangular:mainfrom
leonsenft:fix-signals-test
Closed

test(core): fix expectations that accidentally used incorrect matchers#55294
leonsenft wants to merge 1 commit intoangular:mainfrom
leonsenft:fix-signals-test

Conversation

@leonsenft
Copy link
Contributor

Expect that the number of template executions is === to a number, rather than expect that it does not contain a number. As they were, these expectations would pass regardless of the expected value.

@leonsenft leonsenft marked this pull request as draft April 10, 2024 21:31
@leonsenft leonsenft marked this pull request as ready for review April 10, 2024 21:45
@pkozlowski-opensource pkozlowski-opensource added the area: core Issues related to the framework runtime label Apr 11, 2024
@ngbot ngbot bot added this to the Backlog milestone Apr 11, 2024
Expect that the number of template executions is `===` to a number, rather than expect that it
does not contain a number. As they were, these expectations would pass regardless of the expected
value.
@leonsenft
Copy link
Contributor Author

Fixed the existing formatting issue that prevented submission.

@pkozlowski-opensource pkozlowski-opensource added target: patch This PR is targeted for the next patch release action: merge The PR is ready for merge by the caretaker labels Apr 12, 2024
@pkozlowski-opensource
Copy link
Member

This PR was merged into the repository by commit f2f2c2a.

pkozlowski-opensource pushed a commit that referenced this pull request Apr 12, 2024
#55294)

Expect that the number of template executions is `===` to a number, rather than expect that it
does not contain a number. As they were, these expectations would pass regardless of the expected
value.

PR Close #55294
iteriani pushed a commit to iteriani/angular that referenced this pull request Apr 16, 2024
angular#55294)

Expect that the number of template executions is `===` to a number, rather than expect that it
does not contain a number. As they were, these expectations would pass regardless of the expected
value.

PR Close angular#55294
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators May 13, 2024
@leonsenft leonsenft deleted the fix-signals-test branch October 13, 2025 21:38
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: core Issues related to the framework runtime target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants