If you call it Test::DNSserver ? Not ::server bec that would imply you are a server when you are a client.
In any case, the Check::DNS name does sound more appropriate. IDK about Check::Net::DNS. That implies it's Net::DNS you are checking Perhaps Check::Server::DNS?? I do see a use for TAP. I like the idea of saying ok(soa,"cpan.org") and even ok(ns, "cpan.org" eq [ list of name servers ] ) It is more than object oriented. You use OO to extend TAP I guess but its really logic programming, a rules system I would think we could add this to Nagios or BigBrother. Sent from my BlackBerry® smartphone with Nextel Direct Connect -----Original Message----- From: sawyer x <xsawy...@gmail.com> Date: Sun, 10 Jan 2010 22:16:42 To: Paul LeoNerd Evans<leon...@leonerd.org.uk> Cc: <module-authors@perl.org> Subject: Re: Module naming suggestions : Test::DNS Hi Paul, thanks for answering so quicky! On Sun, Jan 10, 2010 at 8:37 PM, Paul LeoNerd Evans <leon...@leonerd.org.uk>wrote: > Usually the Test:: heirarchy is for unit test modules; mostly things > built on Test::Builder, et.al. True. My module uses Test::Builder as well, and provides comfortable unit tests for DNS queries. Same as Test::Ping or the sort. A major difference between Test::DNS [working title] and most testing modules is that it is object oriented and not functional. I found some modules that work OO as well, but don't remember the names right now. > Such a module would be used to assert on > the behaviour of code under test. > This isn't really to assert Net::DNS's behavior. Quite the contrary, I rely on Net::DNS to have correct behavior. I'm testing DNS records, such as testing ping (Test::Ping), TCP (Test::TCP), file attributes (Test::File) and so on. > I would expect, given the name, that Test::DNS would check the behaviour > of some module, perhaps by asserting it performs DNS queries, or mocking > the results of such. > This module tries to help you run some DNS tests and check some values, such as the Test::File module.
