Ask HN: How do you separate intentional test boilerplate from real duplication?

A deceptively nerdy Ask HN thread turned into a mini courtroom drama over a surprisingly relatable question: when is repeated code in tests just harmless routine, and when is it a sign your project is getting messy? The developer behind an open-source duplicate finder wanted help teaching the tool the difference, and the crowd immediately split into camps.

One side came in with pure “just keep it simple” energy. Why not just skip tests? one commenter basically asked, pointing out that in some languages test files are clearly labeled, so the detector could simply ignore them and move on. Another offered the classic tidy-up answer: if tests keep repeating the same setup, wrap that shared part in a helper function and stop the madness. That’s the practical camp.

But then came the more dramatic twist: some users argued that repeated tests are not always innocent boilerplate at all—they can be a red flag that the tests themselves need a makeover. One commenter said duplicate warnings in test folders often pushed them toward cleaner, easier-to-read parameterized tests instead. In other words: the tool might be annoying, but it may also be right.

The funniest vibe in the thread was the low-key confusion. One user bluntly asked, “What is a structural detector?” which perfectly captured the mood of anyone watching this debate spiral from “simple feature request” into “philosophy of testing.” The real consensus? Everyone wants less noise, but nobody agrees on where useful repetition ends and lazy copy-paste begins.