id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
3971	Verbose testing framework does not say which test it is about to execute	Malcolm Tredinnick	nobody	"Some of the changes I'm making at the moment have the side-effect of breaking tests ''very early'' in their execution (when table flushing fails, for example). The problem is, even when running with -v2, I get no indication of which test it was trying to run. The verbose output only seems shows output that didn't cause the harness itself to fail.

I'm not sure how feasible it is to implement, but it would be nice for times to like this to have a -v3 option that said something like ""About to attempt modeltests.model_forms.models"", so that if I break the harness itself, I know where to look. I had to resort to running each directory in tests/modeltests/ one at a time until I saw the breakage (tests aren't run in any particularly predictable order, that I can see). Not the end of the world, but time consuming and a little tiring the third or fourth time it happened."		closed	Testing framework	dev		wontfix			Accepted	0	0	0	0	0	0