Sourced from com.google.truth:truth's releases.
1.4.0
In this release, our assertions on Java 8 types continue to move from the
Truth8class to the mainTruthclass. This change should not break compatibility for any supported JDK or Android version, even users who test under old versions of Android without API desugaring. Additionally, we will never break binary compatibility, though some users will have to make changes to their source code in order for it to compile against newer versions.This release is likely to lead to more build failures than 1.3.0 did. However, those failures should be straightforward to fix.
Example build failure
Foo.java:152: error: reference to assertThat is ambiguous assertThat(repo.findFileWithName("foo")).isNull(); ^ both method assertThat(@org.jspecify.nullness.Nullable Path) in Truth8 and method assertThat(@org.jspecify.nullness.Nullable Path) in Truth matchSimplest upgrade strategy (if you can update all your code atomically in the same commit as the Truth upgrade)
In the same commit:
- Upgrade Truth to 1.4.0.
- Replace
import static com.google.common.truth.Truth8.assertThat;withimport static com.google.common.truth.Truth.assertThat;.
- If you use Kotlin, replace
import com.google.common.truth.Truth8.assertThatwithimport com.google.common.truth.Truth.assertThat.- Replace
import com.google.common.truth.Truth8;withimport com.google.common.truth.Truth;.
- again, similarly for Kotlin if needed
- Replace remaining references to
Truth8with references toTruth.
- For example, replace
Truth8.assertThat(optional).isPresent()withTruth.assertThat(optional).isPresent().If you're feeling lucky, you can try this one-liner for the code updates:
git grep -l Truth8 | xargs perl -pi -e 's/import static com.google.common.truth.Truth8.assertThat;/import static com.google.common.truth.Truth.assertThat;/g; s/import com.google.common.truth.Truth8.assertThat/import com.google.common.truth.Truth.assertThat/g; s/import com.google.common.truth.Truth8/import com.google.common.truth.Truth/g; s/\bTruth8[.]/Truth./g;'After that process, it is possible that you'll still see build errors from ambiguous usages of
assertThatstatic imports. If so, you can find a workaround in the section about overload ambiguity in the release notes for 1.3.0. Alternatively, you can wait to upgrade until after a future Truth release, which will eliminate the ambiguity by changing the signatures of someTruth.assertThatoverloads.Incremental upgrade strategy
If you have a very large repo or you have other reasons to prefer to upgrade incrementally, you can use the approach that we used inside Google. Roughly, that approach was:
- Make the optional changes discussed in the release notes for 1.3.0.
- For any remaining calls to
Truth8.assertThat, change them to avoid static import.
- That is, replace
assertThat(optional).isPresent()withTruth8.assertThat(optional).isPresent().- Upgrade Truth to 1.4.0.
- Optionally replace references to
Truth8with references toTruth(including restoring static imports if desired), as discussed in section about the simple upgrade strategy above.Optional additional changes
- If you use
assertWithMessage(...).about(intStreams()).that(...),expect.about(optionalLongs()).that(...), or similar, you can remove your call toabout. This change will never be necessary; it is just a simplification.
- This is similar to a previous optional change from 1.3.0, except that 1.3.0 solved this problem for
streamsandoptionals, whereas 1.4.0 solves it for the otherTruth8types.For help
... (truncated)
2e8e488 Set version number for truth-parent to 1.4.0.1f81827 Copy Truth8.assertThat overloads for Path and OptionalLong to the main ...9be8e77 Copy remaining Truth8.assertThat overloads to the main Truth class—except...b02a658 Migrate most usages of Truth8.assertThat to equivalent usages of `Truth.ass...0999369 Automated Code Change7c65fc6 Make it possible to write expect.that(optionalInt).isPresent(), `assertWith...87b371d Bump styfle/cancel-workflow-action from 0.12.0 to 0.12.1