Can I disable a specific domain?

[Nikola-Milovic]

Hey,

I don't like the test coverage domain, it forces the AI to write unnecessary test cases that pollute the test suite and make execution last longer without providing tangible benefits. I prefer to be very methodical and explicit about them. Can we configure this?

[peteromallet]

@Nikola-Milovic, which version are you on? I believe this should have been improved a lot since 0.9.9

[Nikola-Milovic]

I am on latest, 9.12 i believe. But in general, I dont use code cov as measurement since I do a lot of intentional E2E tests instead, so my code coverage is deceptively low. Not sure how this rule is generally enforced, but it's constantly the "worst" score is my codebase.

[peteromallet]

Hey @Nikola-Milovic — good question. There's an existing mechanism that does what you need:

desloppify ignore "test_coverage::*"

This suppresses all test coverage issues. Suppressed issues are excluded from scoring, so the "test health" dimension won't penalize your score.

To undo later: desloppify unignore "test_coverage::*"

A first-class disabled_detectors config key is on our radar but the ignore pattern works well for now. Leaving this open as a feature request for better discoverability.

[Nikola-Milovic]

@peteromallet that works for me, thank you