Test::Class modules, skip install

Herkum has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: Test::Class modules, skip install by dragonchild (Archbishop) on Jun 05, 2006 at 17:23 UTC
Your test modules should go into t/lib/Test/Foo/Bar.pm and you should do a "use lib 't/lib'" in your .t files. That avoids the problem completely. My criteria for good software: Does it work? Can someone else come in, make a change, and be reasonably certain no bugs were introduced?	[reply]
Re^2: Test::Class modules, skip install by adrianh (Chancellor) on Jun 06, 2006 at 10:00 UTC
Your test modules should go into t/lib/Test/Foo/Bar.pm and you should do a "use lib 't/lib'" in your .t files s/should/can/ - installing test modules can be a good thing if they can be useful for people sub-classing your code.	[reply]
Re^3: Test::Class modules, skip install by dragonchild (Archbishop) on Jun 06, 2006 at 13:20 UTC
People subclassing your code should look at your distribution for how to test it. In that case, they'll find your test classes. My criteria for good software: Does it work? Can someone else come in, make a change, and be reasonably certain no bugs were introduced?	[reply]
Re^4: Test::Class modules, skip install by adrianh (Chancellor) on Jun 07, 2006 at 08:21 UTC
Re^5: Test::Class modules, skip install by dragonchild (Archbishop) on Jun 07, 2006 at 14:12 UTC
Some notes below your chosen depth have not been shown here
Re^2: Test::Class modules, skip install by Herkum (Parson) on Jun 05, 2006 at 18:16 UTC
That is a pretty cool idea, thanks! :)	[reply]
Re^2: Test::Class modules, skip install by Ovid (Cardinal) on Sep 11, 2006 at 14:34 UTC
dragonchild wrote test modules should go into t/lib/Test/Foo/Bar.pm. In the "better late than never" category, I figured I should mention a slight problem with this. That path should actually be something like `t/lib/Tests` to avoid potential conflicts with the the `Test::` namespace. I speak from painful experience when I named a base testing class Test::Base. Cheers, Ovid New address of my CGI Course.	[reply]
Re: Test::Class modules, skip install by Old_Gray_Bear (Bishop) on Jun 05, 2006 at 17:32 UTC
Personally, I like modules that install Test Kits. It gives me the feeling that the Developer cares about the quality of the product. Also, it gives me a starting place to find code-snippets (over and above the Examples tab in the POD). ---- I Go Back to Sleep, Now. OGB	[reply]
Re: Test::Class modules, skip install by chromatic (Archbishop) on Jun 06, 2006 at 00:31 UTC
If you intend that anyone should ever subclass your modules, install the test modules. It makes their lives easier.	[reply]
Re: Test::Class modules, skip install by UnderMine (Friar) on Jun 05, 2006 at 22:20 UTC
If you have a test suite you should use it or at least a sub set of it with you package. Regression testing allows you to discover problems at the earliest possible stage. You module may depend on another that has an interface change in a later version. Without including the tests you are relying on the interfaces you use to be backward compatible. Fixing this is a nightmare without a set of tests that show up interface issues. Just my thoughts UnderMine	[reply]
Re^2: Test::Class modules, skip install by Herkum (Parson) on Jun 06, 2006 at 00:06 UTC
It is one thing to have a test suite as part of a package, is another to just be installing tests as regular modules. The point is that in this instance I really don't see a need to install my tests with my package.	[reply]