fix: Fix TestSignalEnvironment to prevent flaky signal tests#2178
Merged
fix: Fix TestSignalEnvironment to prevent flaky signal tests#2178
Conversation
Use registerFirst() so TestSignalEnvironment takes priority over VaadinServiceEnvironment for effect dispatching. Return null from getResultNotifier() so result notifications run synchronously on the calling thread. Use deadline-based polling in runPendingTasks() to handle tasks that arrive after initial queue drain. Re-acquire the session lock before running each task so DOM operations work when effects run directly on the test thread.
caalador
approved these changes
Mar 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use registerFirst() so TestSignalEnvironment takes priority over VaadinServiceEnvironment for effect dispatching. Return null from getResultNotifier() so result notifications run synchronously on the calling thread. Use deadline-based polling in runPendingTasks() to handle tasks that arrive after initial queue drain. Re-acquire the session lock before running each task so DOM operations work when effects run directly on the test thread.