Page MenuHomePhabricator

Add audit coverage reporting in Diffusion
Closed, WontfixPublic

Description

The same way code coverage can be reported line-by-line when browsing a file in Diffusion, it may be interesting to display information about audit coverage that same way.

Of course, report generation per file, per folder, per project of audit coverage may be interesting too.

With some generic support, Diffusion may be able to handle any annotations associated to folders/files/lines with quality data like code complexity, test coverage, audit coverage... So that any extension may add its own measures and render them its own way

Event Timeline

ymartin59 raised the priority of this task from to Needs Triage.
ymartin59 updated the task description. (Show Details)
ymartin59 added projects: Diffusion, Audit.
ymartin59 added a subscriber: ymartin59.
epriestley claimed this task.

Audits are per-commit, not per-file, and having 100% of commits audited isn't necessarily desirable (it's generally not very useful to audit commits which were not made recently).

T4348 discusses possibly building "audit a codebase" workflows. Triggering a codebase audit in this way would presumably have some kind of progress tracking. This is likely a ways off.

I don't think either of these approaches make much sense to turn into a repository-spanning persistent statistic. For a new codebase, you should choose a review/audit policy where every change receives appropriate review, and you can review outstanding audits to see how close you are to 100%.

For an existing codebase, you should do the same, and then possibly combine that with some future workflow per T4348 to cover everything which was committed prior to that point. The codebase-audit would show progress, though, and once that completes you could forget about it since your per-commit policy going forward will provide appropriate review and already has the tools to find outstanding unreviewed stuff.