Consider a new artifact with a lint rule that detects uses of other assertion mechanisms. It probably makes the most sense to ship the rule in a separate artifact in the assertk maven group. Quick Fixes would be appreciated also—especially if they could be batch applied.
kotlin.test assertions
org.junit.Assert
org.junit.jupiter.api.Assertions
The central value in my mind is in discouraging use of assertion mechanisms that ship with testing frameworks. But it might also make sense to extend this rule to flag others assertion libraries in common use like Google Truth, Hamcrest, etc.
The benefits are twofold:
It will help with incremental adoption of assertk in large projects that currently use other systems.
Since the testing frameworks ship with their own assertion libraries, it is very easy for programmers unfamiliar with assertk to reach for those tools instead. A lint check could guide them toward assertk.
Consider a new artifact with a lint rule that detects uses of other assertion mechanisms. It probably makes the most sense to ship the rule in a separate artifact in the assertk maven group. Quick Fixes would be appreciated also—especially if they could be batch applied.
kotlin.testassertionsorg.junit.Assertorg.junit.jupiter.api.AssertionsThe central value in my mind is in discouraging use of assertion mechanisms that ship with testing frameworks. But it might also make sense to extend this rule to flag others assertion libraries in common use like Google Truth, Hamcrest, etc.
The benefits are twofold: