id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc	lang	patch	platform
1900	Change names of 'make' coverage targets	jkeenan	jkeenan	"In the course of work on TT #1893, it was suggested that we change the name of `make cover` to `make fullcover` and the name of `make quickcover` to `make cover`.  This suggestion was based on the observation that the scope of tests run in the current `cover` is much closer to that of the current `make fulltest` than it is to the current `make test`.  `make quickcover`, in contrast, runs a set of tests which is actually a subset of those run by the current `make test`.

Moreover, the current `make cover`, like `make fulltest`, takes a long time to run.  In order to make coverage analysis less onerous -- particularly for the Google Code-In participants who are focusing on boosting test coverage -- it would be better to have `make quickcover` be our '''default''' coverage tool for PMC and C code.

Hence, we should convert as follows:
{{{
make cover     --> make fullcover
# and when that is done ...
make quickover --> make cover
}}}
This task could be handled by a GCI participant.  (I or someone else can mentor.)  Most of the work will be done in ''config/gen/makefiles/root.in''.  My hunch is that many of our intermediate coverage-related `make` targets will not need renaming -- but that's just a hunch.  You should probably first convert `make cover` to `make fullcover`, then verify that that DWIMs, and only then change `make quickcover` to `make cover' (and verify that as well).

Further hunch:  If you `grep` the repository for 'quickcover', you will probably find all the files containing documentation about `cover` or `quickcover`.  These are likely to include, but not be limited to:
{{{
Configure.pl
docs/dev/coverage.pod
config/auto/coverage.pm
t/steps/auto/coverage-01.t
}}}
Thank you very much.

kid51"	bug	closed	normal		testing	2.10.0	medium	fixed