On Mon, 29 Jun 2026 at 15:37, Russell Spitzer <[email protected]> wrote:
> +1 > > I do think these are generally worthwhile. They are also a great help > for consistency. As long as it doesn't require a huge rewrite of the > existing > codebase I think it's worth while gradually switching. > > > I'd propose something like 1. PR to add assertJ to POMs: no source code changes 2. Policy of new test suites to be assertJ only, changes to existing test suites to remain junit. 3. move individual modules to assertj; 4. spotless rules to forbid junit asserts Doing in this order means there'd be a mix of the different asserts for a while, and existing prs would need some work. Getting the AI tools to do a lot of the migration will help.
