in reply to Re: Tests strategies: sharing of resources
in thread Tests strategies: sharing of resources

Thanks for the suggestions and the book reference.

Ikegami: in essence, this would be having a .t file that is actually a control file for running all tests. What I wonder right now about this approach is, how would that fit in the 'make test' generated by module-starter. 'make test' would look at all files in the t/ subdirectory. So that means putting the control file there but all other test files elsewhere outside of t/. Same goes with Narveson's suggestion.

Currently I have all tests in a single file using Test:More. That is fine, but will become kind of ugly as the project grows. This is why I'm trying out module-starter. The modules will probably never be on CPAN but, I'd nevertheless like to adopt an approach which is generalized on CPAN if only to get familiar with it. So I'd like to devise a solution that is compatible and flows nicely.

Maybe that's the solution. As Narveson remarked, might not be that clever, but will keep things going: put some 'control files' in the t/ subdir and have the actual tests in another directory.

  • Comment on Re^2: Tests strategies: sharing of resources

Replies are listed 'Best First'.
Re^3: Tests strategies: sharing of resources
by ikegami (Patriarch) on Dec 29, 2009 at 22:28 UTC

    'make test' would look at all files in the t/ subdirectory.

    I'm pretty sure it only looks for .t files, so placing the modules in a subdirectory of t/ is not a requirement, but it's not a bad idea either.