Assert that the list is not empty - with or without Hamcrest?

java collections junit hamcrest
Prakhar picture Prakhar · Jan 29, 2014 · Viewed 18k times · Source

This is related to Checking that a List is not empty in Hamcrest

I have a question over that - If we can assert the list is not empty without using Hamcrest and just using JUnit as:

assertFalse(list.isEmpty());

Is using 

assertThat(list.isEmpty(), is(false));

or 

assertThat((Collection)list, is(not(empty())));

Worthwhile?

I'm not able to understand are we gaining something using Hamcrest version in this case? Are both equivalent?

Answer

Jeff Storey picture Jeff Storey · Jan 29, 2014

They are the same functionality. The hamcrest provides a more English-like readable language and better error messages. In simple cases like this, I would probably just use the assertFalse

Related questions

Checking that a List is not empty in Hamcrest

I was wondering if anyone knew of a way to check if a List is empty using assertThat() and Matchers? Best way I could see just use JUnit: assertFalse(list.isEmpty()); But I was hoping that there was some way …

Read More
Assert equals between 2 Lists in Junit

How can I make an equality assertion between lists in a JUnit test case? Equality should be between the content of the list. For example: List<String> numbers = Arrays.asList("one", "two", "three"); List<String> numbers2 = …

Read More
JUnit 4 compare Sets

How would you succinctly assert the equality of Collection elements, specifically a Set in JUnit 4?

Read More