Re: Testing: where does the t directory go?

If this is all part of one module, then you probably have something like:

MANIFEST
README
Makefile.PL
lib/Foo/Bar.pm
lib/Foo/Bar/Baz.pm
lib/Blah/Bleh.pm
[download]

If so, just add a t/ subdirectory at the top-level and create your tests there:

t/foo-bar.t
t/foo-bar-baz.t
t/blah-bleh.t
[download]

As long as you're using ExtUtils::MakeMaker to create your Makefile, the normal test process (perl Makefile.PL; make; make test) will then run all your tests.

Note that with tests you might not wind up creating one test file per module, but rather testing areas of functionality which may use several modules at once. The test names I picked above were just an example.

Chris
M-x auto-bs-mode

Comment on Re: Testing: where does the t directory go? Select or Download Code

Replies are listed 'Best First'.
Re: Re: Testing: where does the t directory go? by jplindstrom (Monsignor) on May 30, 2002 at 18:16 UTC
Ah-h-h! My thinking was flawed; I tought of the classes as kind-of-semi-separated from each other, when it makes sense to consider the application's classes a single module. Many thanks! /J	[reply]