I don't know why this didn't occur to me before, but why not put this in a
Wiki? It seems to be a _huge_ pain to mail this list out every few weeks
whenever something changes, why not post it up and allow people to mark it
up a little: say that they are working on a test so the effort isn't
duplicated, or remove items from the list once they are tested.

Also, how does one test Net::Ping when we can't guarantee a server to ping?

Zach

On 9/18/01 7:57 PM, "Michael G Schwern" <[EMAIL PROTECTED]> wrote:

> Here's where we're at.  I might be a little off on the Pod:: tests.
> 
> chromatic and Andrew Wilson took a good chunk out of it.  CGI is now
> pretty well covered.  More of ExtUtils are tested, and rather
> amazingly, Term::Complete!
> 
> For Term::ReadLine you may be able to steal/draw inspiration from the
> Term::ReadLine::Perl and Term::ReadLine::Gnu tests.
> 
> 
> AutoSplit
> CPAN
> CPAN::Nox
> DB
> Dumpvalue
> ExtUtils::MM_*
> ExtUtils::Embed
> ExtUtils::Install
> ExtUtils::Installed
> ExtUtils::Liblist
> ExtUtils::Mkbootstrap
> ExtUtils::Mksymlists
> ExtUtils::MM_*
> ExtUtils::Packlist
> filetest
> Net::Cmd
> Net::Config
> Net::Domain
> Net::Netrc
> Net::Ping
> Net::POP3
> Net::Time
> open
> Pod::Checker
> Pod::Find
> Pod::Functions (no docs!)
> Pod::Html
> Pod::InputObjects
> Pod::LaTeX
> Pod::Man
> Pod::ParseUtils
> Pod::Select
> Pod::Text::*
> Pod::Usage
> sigtrap
> Term::Cap
> Term::ReadLine
> Tie::Scalar
> warnings::register (almost no docs)
> 

Reply via email to