how to avoid warnings from import static org.assertj.core.api.Assertions.assertThat;

[pmendelson]

Form day 1 i have always created tests with this pattern

import static org.assertj.core.api.Assertions.assertThat;

public class TestClass {
  @Test
  public void testMethod() {
    String tstStr = null;
    assertThat(tstStr).isNull();
  }
}

Using the static import allows my tests to look more natural.

Recently some of the assertThat signatures have been deprecated. Therefore when I look at my code in an IDE like eclipse i get warnings about my static import.

Are their any recommendations to avoid this warnings without having to write

Assertions.assertThat(tstStr).isNull();

[pmendelson]

After I wrote this thread I decided to read the javadoc. I now see 2 replacement classes, AssertionsForClassTypes and AssertionsForInterfaceTypes.

Thanks for providing such a useful library

[scordio]

I couldn't reproduce the issue but I'm using IntelliJ IDEA. Could it be an Eclipse specific issue?

That's what I see in IntelliJ:

[pmendelson]

It could be an eclipse issue but whether it's an eclipse bug or a "normal" reaction to some, but not all, assertThat signatures being deprecated is open to debate

I have no plans to stop using eclilpse or assertj but i'd love to find a way to eliminate this warning.

[scordio]

Has something similar been reported to Eclipse? With a quick search, I could find only groovy/groovy-eclipse#1478.