] http://search.cpan.org/dist/Config-Context/
http://search.cpan.org/dist/CGI-Application-Plugin-Config-Context/
http://search.cpan.org/dist/CGI-Application-Plugin-AnyTemplate/
[2] HTML::Template is required because it's already a prerequisite of
CGI::Application
--
Michael Graham [EMAIL
another caveat with the PersistentPerl approach - END blocks seem
only to run on the first request.
Michael
---
Michael Graham [EMAIL PROTECTED]
, global vars; 'require'd code only gets loaded on the
first request, etc.
* Test scripts have to end in a true value.
If there's interest, I'll try to package all this up into a CPAN module.
Michael
---
Michael Graham [EMAIL PROTECTED]
, I haven't yet found one
that requires Test::URI.
Michael
---
Michael Graham [EMAIL PROTECTED]
or any other stock test boilerplate. If there's something left
over, then the module probably has an actual test suite.
Michael
---
Michael Graham [EMAIL PROTECTED]
$ prove -Ilib -It/prereq_lib t/
Michael
--
Michael Graham [EMAIL PROTECTED]
difference in kwalitee between a module that has
only the default tests and a module with a hand-crafted test suite. One
of the first things I do when checking out a new module is to check if
there are more than three files in the t/ directory.
Michael
---
Michael Graham [EMAIL PROTECTED]
dependencies, but that's
probably not a big deal. If someone uses my module but doesn't list it
in recommends, and I want my prereq point, then I'll bug them to add it.
Michael
---
Michael Graham [EMAIL PROTECTED]
'is_prereq' point.
Don't make us release this foolishness outside of ACME::!
Michael
---
Michael Graham [EMAIL PROTECTED]
Michael Graham wrote:
Another good reason to ship all of your development tests with code is
that it makes it easer for users to submit patches with tests. Or to
fork your code and retain all your development tools and methods.
Perl::MinimumVersion, which doesn't exist yet, could check
be directed to [EMAIL PROTECTED]
Michael
---
Michael Graham [EMAIL PROTECTED]
YAPC::NA 2005 Toronto - http://www.yapc.org/America/ - [EMAIL PROTECTED]
---
are considered 'kwalitudinous' on my system.
Maybe I don't know enough about testing and module development to know
that the module still works fine in spite of the failed POD test.
Michael
---
Michael Graham [EMAIL PROTECTED]
YAPC
be a different way of marking additional private
methods?
Michael
--
Michael Graham [EMAIL PROTECTED]
($pid) {
my $ret = waitpid($pid, 0);
return $ret;
}
do $script or die Compile errors: $script: [EMAIL PROTECTED];
exit;
}
Michael
--
Michael Graham [EMAIL PROTECTED]
with it
particuarly the Test::Builder::Tester guys.
Would this make it possible to run many test scripts (each with its own
plan) within the same perl process? 'Cos that would be nifty.
Michael
--
Michael Graham [EMAIL PROTECTED]
to play with for a couple of hours.
Michael
--
Michael Graham [EMAIL PROTECTED]
use:
$ cat runtests
#!/bin/sh
prove -I/path/to/modules -MTestConfig $*
Which is (very) slightly cleaner.
Michael
--
Michael Graham [EMAIL PROTECTED]
17 matches
Mail list logo
