Hi James and Randy,
Thank you so much for your replies!
Yes, the modules that we are testing are not for
standard distribution. They are created by other folks
in my organization to support and to be part of our
current automated integration system. They are our
internal use. There already are ma
James E Keenan wrote:
Scott Wang wrote:
Hi Chris,
I am still confus.
For example,
On my Linux box, I have a module
"/tmp/experiment/lib/module_to_test.pm" to be tested, and I have two
Perl unit test scripts "/tmp/experiment/tests/test1.pl" and
'"/tmp/experiment/tests/test2.pl" to load the
Scott Wang wrote:
Hi Chris,
I am still confus.
For example,
On my Linux box, I have a module "/tmp/experiment/lib/module_to_test.pm" to be tested, and I have two Perl
unit test scripts "/tmp/experiment/tests/test1.pl" and '"/tmp/experiment/tests/test2.pl" to load
the module_to_test.pm module
On Dec 25, 2005, at 3:46 PM, Scott Wang wrote:
I am new to use Devel::Cover.
We have lots of product Perl modules in our product "lib" folder
and we have lots of Perl test scripts to cover those modules, right
now, we are trying to get the code coverage metrics for our tests
on those modu
Hi Chris,
I am still confus.
For example,
On my Linux box, I have a module "/tmp/experiment/lib/module_to_test.pm" to be
tested, and I have two Perl unit test scripts "/tmp/experiment/tests/test1.pl"
and '"/tmp/experiment/tests/test2.pl" to load the module_to_test.pm module and
execute the su
Thanks for all your helps.
I am new in Perl world, my situation is, for example:
- my modules, which I like to test, live in "tmp/experiment/lib" folder
- my test scripts, which are created to load and exercise the above modules,
live in "tmp/experiment/tests" folder
- I call our internal test h
