2023-05-03 11:06:20 +02:00
== Why is this an issue?
2021-04-28 16:49:39 +02:00
AssertJ assertions methods targeting the same object can be chained instead of using multiple ``++assertThat++``. It avoids duplication and increases the clarity of the code.
This rule raises an issue when multiples ``++assertThat++`` target the same tested value.
2021-04-28 18:08:03 +02:00
2023-05-03 11:06:20 +02:00
=== Noncompliant code example
2021-04-28 16:49:39 +02:00
2022-02-04 17:28:24 +01:00
[source,java]
2021-04-28 16:49:39 +02:00
----
assertThat(someList).hasSize(3);
assertThat(someList).contains("something");
----
2021-04-28 18:08:03 +02:00
2023-05-03 11:06:20 +02:00
=== Compliant solution
2021-04-28 16:49:39 +02:00
2022-02-04 17:28:24 +01:00
[source,java]
2021-04-28 16:49:39 +02:00
----
assertThat(someList)
.hasSize(3)
.contains("something");
----
2021-04-28 18:08:03 +02:00
2021-09-20 15:38:42 +02:00
ifdef::env-github,rspecator-view[]
'''
== Implementation Specification
(visible only on this page)
2023-05-25 14:18:12 +02:00
=== Message
Join these multiple assertions subject to one assertion chain
=== Highlighting
* Primary location: first assertThat
* Secondaries: all subsequent assertThat
2021-09-20 15:38:42 +02:00
endif::env-github,rspecator-view[]