eb167695

By: Tom Sydney Kerckhove <syd@cs-syd.eu>

Say where a test helper can go

The rule said what it wanted and why, and left the operator to work out
where the helper should actually end up. That is the part that takes the
time: a let in the it, inlining it, a let in the describe, a .Gen module,
a .TestUtils module, and no way to tell from the finding which one this
helper wants.

So the why lists them, best first. Only the text changes; what the rule
reports is what it reported before.
e2e-added-rule-is-rune2e-artifacts-are-reade2e-choices-are-found-beside-the-repositorye2e-cleane2e-dirty-package-is-judged-failinge2e-dirty-project-is-judged-failinge2e-dirty-report-is-readablee2e-disabled-rule-is-not-rune2e-incomplete-artifacts-are-a-failuree2e-judging-nothing-failse2e-named-packages-are-every-packagee2e-no-packages-is-judged-failinge2e-no-store-paths-in-findingse2e-paths-are-repository-relativee2e-withheld-facts-faile2e-wrong-source-mapping-is-a-complainthlint-checkhopinionpre-commitreleaseshellweeder-checkconfiguredevShelldefaultx86_64-linux