(fixes #3464) Replace assert() usages with assertThat() #5861
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.
Uses of the
assert()
function in Kotlin are inherited from Java and are only enabled in the JVM with the-ea
flag (enable assertions). Since the-ea
flag has "not been enabled and won't be", these currentassert()
assertions don't do anything.To fix this the
assertThat()
assertion is always active, regardless of JVM settings, so this would be more suitable.Fixes #3463
What changes did you make and why?
assert()
function to equivalentassertThat()
function calls, in 3 relevant files.assetThat()
,equalTo()
, andnot()
, in these files for translating the current assertions over to the hamcrest syntax.Tests performed
Tested
ProdDebug
on Pixel 9 with API level 34.