In article <20011021000950.I588@blackrider>, "Michael G Schwern" <[EMAIL PROTECTED]> wrote:
> For libnet it happens to work out that the untestable part (the network > connection) is incidental. The testable part (the protocol) is essential. > That's the sweet spot. If we can seperate the net connection from the > protocol, we've got it made. No need for elaborate skip tests and assumptions > about platforms. chromatic did just that. Er, actually, chromatic just fat-fingered Socket::inet_ntoa() and Socket::inet_aton(). (Yeah, they don't really require nameservers. No, the real ones don't resolve names to packed addresses. Hey, it's a *feature* that you can send bad data in the test and still test the module. That's how powerful Mock Objects are.) While my heart's definitely in the right place, I pulled a Homer on this one. Thanks, though. So far, I have tests for Net::Time and Net::Config. Easy stuff. > So we can test libnet. We can do it on all platforms. We don't have to muck > about with any more $^O hackery than usual. Most tests will involve writing > some sort of dummy server. For some, this will be easy (Net::Ping, Net::Time) > for others it might be hard (Net::FTP), but it's possible. Agreed. The rest of you hop to it! Please? -- c
