I replaced the line in my build.gradle file that declared using Fest-Android with one for AssertJ-Android:

-    androidTestCompile('com.squareup:fest-android:1.0.+') {
+    androidTestCompile('com.squareup.assertj:assertj-android:1.0.0') {

The issue is that after replacing all static imports of import static org.fest.assertions.api.ANDROID.assertThat; with import static org.assertj.android.api.Assertions.assertThat;, the static import isn't found therefore my Robolectric tests fail to compile. If I change the Gradle line to use compile instead of androidTestCompile, the tests work correctly but obviously that's not optimal nor what the documentation describes.

The error returned by javac is the following:

File.java:∞ error: package org.assertj.android.api does not exist
import static org.assertj.android.api.Assertions.assertThat;
                                     ^

After pulling the git repository and opening in Android Studio, I get the following error when trying to sync the project with Gradle:

These modules are in different directories, so I'm pretty confused as to why AS would think they are in the same path.

Anytime i try to sync my gradle i get this message

Error:Conflict with dependency 'com.android.support:support-annotations'. Resolved versions for app (23.1.1) and test app (22.2.1) differ. See http://g.co/androidstudio/app-test-app-conflict for details.

These i believe are the essential excerpts from my gradle file

testCompile 'junit:junit:4.12'
    testCompile 'org.robolectric:robolectric:3.1-SNAPSHOT'
    testCompile 'org.assertj:assertj-core:3.3.0'
    testCompile 'com.squareup.assertj:assertj-android:1.1.1'

compile 'com.android.support:appcompat-v7:23.1.1'
    compile 'com.android.support:recyclerview-v7:23.1.1'
    compile 'com.android.support:cardview-v7:23.1.1'
    compile 'com.android.support:support-v4:23.1.1'

The POM pushed to Maven central contains this dependency:

<dependency>
      <groupId>com.android.support</groupId>
      <artifactId>support-v4</artifactId>
      <version>19.1.+</version>
      <scope>compile</scope>
</dependency>

The version format 19.1.+ is illegal in Maven (i know it comes from Gradle). Please consider modifying the version number.

This updates the following library and build tool versions:

• Gradle: 2.9 → 3.2
• Source repositories: mavenCentral → jcenter
• Android Plugin for Gradle: 1.5.0 → 2.2.2
• Android Build Tools: 23.0.2 → 25.0.0
• Android Support Libraries: 23.1.1 → 25.0.1
• Android SDK: 23 → 25

This also drops support for Java 7, which is no longer support by Android Plugin. (See AOSP issue 224738.)

Android has same values for flags FLAG_ACTIVITY_MULTIPLE_TASK and FLAG_RECEIVER_NO_ABORT. Hence, any invocation of hasFlags resulted in IllegalStateException being thrown.

Try, for example:

  @Test
  public void test() {
    assertThat(new Intent().addFlags(Intent.FLAG_ACTIVITY_BROUGHT_TO_FRONT))
        .hasFlags(Intent.FLAG_ACTIVITY_BROUGHT_TO_FRONT);
  }

I believe we also need a project with integration tests. Where this test could be written. I personally created one to test your code from master branch. But I do not submit it here: it uses robolectric. Should I submit it? I really do not know whether this change will break something in other place. The project definitely lacks tests IMHO...

Was just writing a test and really wanted to write something like:

assertThat(viewGroup).has(textView).withText("fest!");

or perhaps

assertThat(viewGroup).has(TextView.class).withText("fest!");

is better design.

Have you thought about supporting AssertJ instead of/in addition to fest-assert-2.x? fest-assert-2.x is dormant and if it comes to life again chances are it is going to be less useful (there are plans to remove a lot of assertions, see https://github.com/alexruiz/fest-assert-2.x/issues/159 and https://github.com/joel-costigliola/assertj-core#why-have-we-forked-fest-assert). I'd be willing to provide a patch, but it would be a breaking change (packages have to be renamed) and eventually involve renaming the project to assertj-android.

Should address #166

Is there any guidelines for knowing if I've covered all the APIs / methods that I need to for a given class? I just sorta guessed at ones that people might actually use (IE: Does there need to be a getBackgroundTintList() for FAB?)

Sometimes fails with messages like: "Expected text but was " This happens because the text is actually a CharSequence that doesn't compare nicely with String. In my case it was a SpannableStringBuilder. Maybe a nice way to fix this would be to check whether the 'text' parameter is actually a String and call toString() on actualText before doing the comparison:

public S hasText(CharSequence text) { isNotNull(); CharSequence actualText = actual.getText(); if (text instanceOf String) actualText = actualText.toString(); assertThat(actualText) // .overridingErrorMessage("Expected text <%s> but was <%s>.", text, actualText) // .isEqualTo(text); return myself; }

That way in the 1% case where someone really wants to ensure that a text field has some exact configuration of a SpannableStringBuilder as it's text they can still build one up and pass it in, while the rest of the time we'll get the String comparison we'd intuitively expect.

Hey guys,

First time trying to use this lib. Dropped the dependency in my pom, wrote a quick test just to inflate a View into an Activity, and assert that it isn't null. When I try to compile, I get the error:

class file for android.app.TaskStackBuilder not found

I've only tried a single assertion:

assertThat(view).isNotNull();

the error points back directly to this line.

Basically a copy of preference assertions from module assertj-android/,

• minus some classes/methods not included in preference-v7
• plus SwitchPreferenceCompat.

I keep getting the following warning:

WARNING: Module 'com.squareup.assertj:assertj-android-design:1.1.1' depends on one or more Android Libraries but is a jar
WARNING: Module 'com.squareup.assertj:assertj-android-support-v4:1.1.1' depends on one or more Android Libraries but is a jar
WARNING: Module 'com.squareup.assertj:assertj-android-appcompat-v7:1.1.1' depends on one or more Android Libraries but is a jar

From #156:

This seems to have removed

<packaging>aar</packaging>

from the POM file. As a result we get a Gradle build error

version com.squareup.assertj:assertj-android-support-v4:1.0.1-SNAPSHOT depends on libraries but is a jar

It looks like with API 21 some of receiver flags have same values as activities flags (FLAG_RECEIVER_NO_ABORT, FLAG_ACTIVITY_MULTIPLE_TASK for example). This actually breaks BitMaskStringBuilder since it expects unique values.