Hi Ian, Test::Unit was a nice idea, but it's been abandoned.
Test::Inline seems nice, but it doesn't give you the full benefits of Test::Class (convenient setup, teardown, inheritance, etc.). Test::Class is great. I'm quite happy with it. If you're more comfortable with XUnit style testing, this is the way to go. However, read the docs for caveats. Test::More is also good if you're doing smaller projects. All of my CPAN modules now require Test::More. It's very easy to use and you can get up to speed faster with Test::More than most of the other testing tools (besides Test::Simple). Cheers, Ovid --- Ian Langworth <[EMAIL PROTECTED]> wrote: > I'm taking a software development class this semester which will > involve > writing extensive object-oriented code. My partner and I are trying > to > decide whether to use Test::Unit, ::Class, or ::Inline for our test > scripts. > > I can see the advantages of Test::Class in terms of object heirarchy, > > but I really like the idea of having my tests right along with the > methods when using Test::Inline. (The latter would be great when > presenting our code to the class.) > > Thoughts? > > -- > Ian Langworth > Project Guerrilla > Northeastern University > College of Computer and Information Science > > ===== If this message is a response to a question on a mailing list, please send follow up questions to the list. Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
