Fix Flaky Test SpannerPersistentPropertyImplTests#testNullColumnName#4214
Merged
jinseopkim0 merged 1 commit intoGoogleCloudPlatform:mainfrom Nov 11, 2025
Merged
Conversation
pem70
force-pushed
the
fix-testNullColumnName
branch
from
ee5124b to
27453c7
Compare
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.
Issue
Test
SpannerPersistentPropertyImplTests#testNullColumnNameis flaky. See #4213Fix
This fix drops brittle message checks (including dynamic Mockito class names) and instead asserts stable parts of the error plus a regex that accepts any of the expected property names. It still verifies that an exception is thrown for a null field name on TestEntity and that the message references the entity/property, but no longer fails due to environment-dependent wording.