...
- info on how a new rule compares to the full *existing* ruleset
- overlaps between rules, using "hit-frequencies -o"
- collated results across all users' corpora, which can be broken down to view each user separately or all together
- checked rules and their results are kept in a version-control history, so benefits of VC are available
- ongoing visibility of hit-rates of the existing ruleset, against fresh corpora
The ruleqa CGI is now in the SpamAssassin zone, so this is still visible, even though the automc stuff is disabled. Here it is: http://buildbot.spamassassin.org/ruleqa/
...
Someway of scheduling a small run during the development day would be useful, rather than waiting for the nightly. An email of users completed results would be nice to see too.
JustinMason: I think the more immediate, email-based, system is better done using the faster preflight system, as below; this one is good for slow-but-comprehensive daily tests. the "preflight" system provides the "small run" option – see below!
Preflight Mass-Checks
See RulesProjBuildBot.
...