packages
packages copied to clipboard
[espresso]: Bump com.google.truth:truth from 1.0 to 1.1.3 in /packages/espresso/android
Bumps com.google.truth:truth from 1.0 to 1.1.3.
Release notes
Sourced from com.google.truth:truth's releases.
1.1.3
- Fixed a bug in how
comparingExpectedFieldsOnly()
handlesoneof
fields. (f27208428)- Improved
comparingExpectedFieldsOnly
to work when required fields are absent. (f27208428)- Changed
Subject.toString()
to throwUnsupportedOperationException
. (fa4c7b512)1.1.2
This release completes the feature that I got wrong in 1.1.1 -- the ability to exclude our JUnit 4 dependency and still use standard Truth assertions.
- Made it possible for users to exclude our JUnit 4 dependency and still use standard Truth assertions -- really this time, even in cases in which excluding the dependency failed under 1.1.1. (JUnit 4 is still required for some advanced features, like
Expect
,ExpectFailure
, andTruthJUnit.assume()
.) (948f3edca)- When JUnit 4 is excluded from the classpath, the
AssertionError
Truth generates as a substitute forComparisonFailure
now includes the expected and actual values that were missing in 1.1.1. (6b0140730)1.1.1
We recommend not trying to exclude our JUnit dependency even under this release. We will release 1.1.2 with better handling for the missing dependency shortly.
Made it possible for users to exclude our JUnit 4 dependency and still use standard Truth assertions. (JUnit 4 is still required for some advanced features, likeExpect
,ExpectFailure
, andTruthJUnit.assume()
.) (2d65326ec)
- Update: This appears to let users exclude the dependency in some cases but not all. We are working on a fix.
- Update 2: Also, even if you succeed in excluding the dependency in your environment, you will see failure messages that are missing information. We have a fix for this ready.
If you wish to exclude our JUnit dependency, you may wish to consider this alternative approach. That approach may be worthwhile even after we fix the bugs described above.
I apologize for the trouble.
1.1
- Fixed (we think :)) R8 compilation failure:
Error: com.android.tools.r8.errors.b: Compilation can't be completed because `org.objectweb.asm.ClassVisitor` and 1 other classes are missing.
(0bfa285fa)- Added
unpackingAnyUsing(TypeRegistry, ExtensionRegistry)
. If you call this method,ProtoTruth
will attempt to unpackAny
messages before comparing them. (b50d878b)- Added
formattingDiffsUsing
methods toIterableSubject
andMapSubject
. This allows you to get failure messages which show diffs between the actual and expected elements (like you get withcomparingElementsUsing
) while still comparing them using object equality. (ae997be77)- Changed Checker Framework annotations from
checker-qual
toqual
. (e71b57b9f) With this change, we inadvertently introduced Java 8 bytecode into our dependencies. Please report problems on #882. Sorry for the trouble.- Added null checks to
StringSubject
. (3481ab0af)- Included ASM as a dependency (non-
<optional>
) by default. It is still safe to exclude if you want to minimize dependencies, but by including it, you may see better failure messages. (aea78e81c)- Removed dependency on
gwt-user
. (b54e9ef50fe670bf93dd3b2b6851423be631b429)- API documentation for Truth classes is now easier to reach. For example, for
StringSubject
, visit truth.dev/StringSubject. Also, more easily access the index at truth.dev/api.1.0.1
- Changed failure messages to identify trailing whitespace in failed string comparisons. (7a58a45b)
- Moved
gwt-user
totest
scope. (51bbbf42)- Fixed handling of proto maps with keys equal to the key type's default value. (8ebfe2ab)
- Worked around what seems to be a classloading bug in old versions of some vendors' Android runtimes. (02c5e79925d455331377f3e6640cc450aecf6774)
Commits
- See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!).
If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?
Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version
or @dependabot ignore this minor version
. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore
condition with the desired update_types
to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.