Tune down tests.duplicate-mock-setup

[jesse-black]

I'm finding the majority of issues reported on my codebase are tests.duplicate-mock-setup, but for tests DAMP over DRY is generally preferable so that each individual test is readable in isolation.

[benvinegar]

Totally fair, I have the same concerns. Will re-investigate.

[benvinegar]

What if we had --omit-tests?

I agree in principle but a challenge is: this rule gives 0 for 7/8 of the mature OSS repos. Whereas it lights up like a Christmas tree for the AI repos. Trying to make this less about vibes / feels about what's good or what's not good; the data says it's an indicator.

[jesse-black]

I would still want to scan tests so maybe a way to configure exclusions on a rule by rule basis?

I wonder how many of the mature oss repos are gating CI on test coverage? I have gates set up for 90% line coverage on new/changed code. And AI repos might be more likely to configure coverage gates because it's easy to simply generate enough tests to hit them. I wonder if that's what it's picking up on?