Re: [Module-build-general] RFC: Build test test_dirs=(list)

[Steve P. <sp...@qu...>]

On Tuesday, August 12, 2003, at 10:35  pm, David Carmean wrote:

> If I want to test only the methods in the parent class Foo::Bar::One,
> I run "Build test test_dirs=t/Foo/Bar/One/t".   If I want to run
> the tests for that class and all it's children, I run
> "Build test test_dirs=t/Foo/Bar/One".  If I'm fixing a bug in 
> Foo::Bar::One::B,
> I run "Build test test_dirs=t/Foo/Bar/One/B/t" over and over, and then 
> when I'm
> satisfied I run a full regression test with "Build test".

That works fine if you organize tests by directory, but a lot of 
authors like to group their tests by function in the /t directory - 
M::B's suite is a good example of that:

	t/basic.t
	t/compat.t
	t/runthrough.t
	...

And I know a lot of people (myself included) who also like to number 
them according to priority.  So for example, you might see something 
like:

	t/01..basic.t
	t/02..framework.t
	t/03..foo-bar.t
	...

Using regexps on the path to the test script would let you specify a 
subset of tests to run in all of these scenarios:

	./Build test matching=t/Foo/Bar/One
	./Build test matching=runthrough
	./Build test matching=t/0*

Which could be handy.

-Steve