truth.dev

What It Is

Truth is a testing assertion library for Java and Android, owned and maintained by the Guava team. The documentation says it is used in most tests within Google’s own codebase. It replaces native JUnit assertions such as assertEquals with a fluent API like assertThat(actual).contains(...), aiming to make assertions easier to write and read while providing more diagnostic failure messages.

Core Capabilities

Truth focuses not on piling up a huge number of assertion methods, but on providing a smaller, consistent API for common types. It supports assertions for collections, Maps, Multimaps, strings, floating-point numbers, Java 8 types, and more, with dedicated pages such as Fuzzy Truth, Proto Truth, and Floating Point covering special comparison scenarios. Compared with Hamcrest, it relies on chained method calls, allowing IDEs to autocomplete based on the object type. Compared with AssertJ, Truth has a smaller API and emphasizes that “most tasks should have only one way to do them.” It also supports Android by default and additionally supports GWT.

Integration, API, and Documentation

Usage is straightforward: add com.google.truth:truth:1.4.5 via Maven, or use testImplementation with Gradle and fetch it from Maven Central. Core entry points include Truth.assertThat and assertWithMessage; for advanced scenarios, users can use about(...), Expect, custom Subject implementations, and FailureStrategy. The documentation is high quality, covering FAQs, Javadocs, supported types, extension guides, and detailed comparisons with AssertJ and Hamcrest. It also explains common anti-patterns and recommendations for Error Prone static analysis.

Pricing and Open Source

The source text does not mention commercial pricing; Truth is used as a testing dependency. The page provides links to the GitHub source code and GitHub issues, indicating that development and issue tracking are open on GitHub. License information was not present in the captured text.

Pros, Cons, and Who It’s For

Its strengths include concise syntax and context-rich failure messages. For example, collection differences can show missing, expected, but was, and multimap contents. Direct Android support also lowers the cost of testing for mobile projects. Limitations include a smaller built-in assertion surface than AssertJ; containsExactly does not check ordering by default and requires appending .inOrder(); and its looser typing may allow some test issues to avoid compile-time detection. Truth is a good fit for Java, Android, and GWT teams, as well as projects that care about test readability and efficient failure diagnosis.

Access from China

The source text does not provide information about domestic network access or payment. As a tool in the Maven Central/GitHub ecosystem, its usability in China depends on network access to Maven Central, GitHub, and the project site. If access is unstable, teams can consider enterprise Maven mirrors or alternatives such as AssertJ, Hamcrest, or native JUnit assertions.