In `ExpectFailure`, never generate "value of" lines based on bytecode.

The immediate motivation here is to prevent cl/801287069 and similar changes from affecting "value of" lines seen by users who are testing their own `Subject` implementations. But this is something that we've wanted before, including to make behavior consistent between the JVM (under which we can read bytecode) and other platforms (under which we can't/don't).

RELNOTES=Changed `ExpectFailure` to never generate "value of" lines based on bytecode. This slightly simplifies writing new tests with `ExpectFailure` and prevents future behavior changes in some `ExpectFailure` tests that already exist. However, it may also require changes to other existing `ExpectFailure` tests to remove or change any assertions about the "value of" line.
PiperOrigin-RevId: 802995279
5 files changed
tree: a383aa7713bfeb006e780229db1798ba5a6e48b5
  1. .github/
  2. core/
  3. extensions/
  4. javadoc-link/
  5. refactorings/
  6. util/
  7. .gitignore
  8. CONTRIBUTING.md
  9. LICENSE
  10. overview.html
  11. pom.xml
  12. README.md
README.md

Main Site Build Status Maven Release Stackoverflow

What is Truth?

Truth makes your test assertions and failure messages more readable. Similar to AssertJ, it natively supports many JDK and Guava types, and it is extensible to others.

Truth is owned and maintained by the Guava team. It is used in the majority of the tests in Google’s own codebase.

Read more at the main website.