using assertj for better test matchers - objections?

[P. Ottlinger]

Hi,

does anyone object that we use assertj for mor expressive testing matchers?

I just stumbled upon:

        assertTrue(change.getChanges().size() == 1);

which would be more clear as
assertThat(change.getChanges()).isNotNull().isNotEmpty().hasSize(1);


Any objections if I add assertJ in test-scope?

Cheers,
Phil