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.
