A deprecated set of AssertJ assertions for testing Android UI components with readable error messages.
AssertJ Android was a library that extended AssertJ to provide specialized assertions for testing Android UI components. It offered domain-specific assertions for views, layouts, and support library objects, making test code more readable and expressive. The project is now deprecated in favor of Google's Truth library.
Android developers writing unit and instrumentation tests who want more readable assertions and failure messages for UI components.
It provided Android-specific assertions with human-readable error messages and a fluent API, reducing the boilerplate of traditional JUnit or AssertJ tests. However, it's deprecated due to maintenance challenges and the superior extensibility of Truth.
A set of AssertJ helpers geared toward testing Android.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Produces descriptive error messages like 'Expected visibility <gone> but was <invisible>' instead of numeric codes, making test failures easier to debug and understand.
Allows chaining multiple assertions on a single Android object, such as views or layouts, reducing boilerplate and improving test code conciseness.
Includes specialized assertions for nearly every Android component, from core views to support library modules like AppCompat and RecyclerView, based on the README examples.
Provides a clear pattern for extending assertions to custom Android controls, as shown in the README with example code for a CustomLayoutAssert class.
The project is no longer maintained, with the creators explicitly recommending Google's Truth instead, meaning no bug fixes, updates, or support for new Android versions.
As admitted in the README, the rapid development of Android support libraries and Play Services made it unsustainable to keep the library current, leading to its deprecation.
The README states that AssertJ's model for supporting alternate assertions is not a good practice compared to Truth's superior extensibility, which limits future customization.
Requires separate dependencies for different Android libraries (e.g., support-v4, Play Services), complicating build configurations and increasing dependency management overhead.