detekt/detekt
Auf GitHub ansehen`OutputReportsSpec.kt` tests has really little sense
Open
#8.625 geöffnet am 8. Sept. 2025
corehelp wantedhousekeeping
Repository-Metriken
- Stars
- (6.942 Stars)
- PR-Merge-Metriken
- (Durchschn. Merge 4T 9h) (65 gemergte PRs in 30 T)
Beschreibung
Reviewing OutputReportsSpec.kt I'm not sure what those tests are really testing.
- There is not file/class called
OutputReportsso they aren't testing that OutputReportis the class more near to it. But those tests never execute nothing related with that.- It execute
ReportsSpec. But that's an interface with no public/internal implementation. - It also executes
ReportsSpecBuilderbut that code is indetekt-toolingand these tests are endetekt-core.
Also, OutputFacadeSpec only has one test and it's to the ones in OutputReportsSpec.
We need to review this part of the code. Remove or move the tests that have no sense and create real tests to check how the reports (ConsoleReport and OutputReport) work.