To continue our journey to improve the overall quality of test code, we should continue to cover more testing libraries.
We should target libraries frequently used by developers, AssertJ is a good candidate heavily used by the community.
AssertJ documentation provides a list of incorrect usage, it can be used as inspiration for creating relevant rules.
In addition, some of the rules targeting JUnit could be rethought/adapted to target AssertJ as well.
The issues will be reported at the same place as the issues on the main code, as it is already the case for existing rules targeting test code.
Since they target specifically test code, the impact on SonarQube/SonarCloud should be minimal.