id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc	lang	patch	platform
759	Reconsider one-test-file-per-PMC policy	jkeenan	coke	"''test_file_coverage.t'' was added by particle in January 2006.
{{{
------------------------------------------------------------------------
r11227 | particle | 2006-01-17 14:26:47 -0500 (Tue, 17 Jan 2006) | 3 lines

tests: test file coverage
~ tests that all PMC classes have test files
}}}
It requires that files matching ''src/pmc/*.pmc'', ''src/dynpmc/*.pmc'' and ''src/dynoplibs/*.ops'' have corresponding test files in ''t/pmc'', ''t/dynpmc'' and ''t/dynoplibs'', respectively.

The coding standard implied by this test file was little noticed and uncontroversial until just this week.  However, discussion on the parrot-dev list suggests that certain PMCs should be exempt from this requirement.  I am creating this ticket to track discussion of the issue.

Thank you very much.[[BR]]
kid51"	todo	closed	normal		coding_standards	1.2.0	medium	fixed		coke whiteknight particle