Read more
Is there any sexier topic in software development than software testing? That is, besides game programming, 3D graphics, audio, high-performance clustering, cool websites, et cetera? Okay, so software testing is low on the list. Andthat's unfortunate, because good software testing can increase your productivity, improve your designs, raise your quality, ease your maintenance burdens, and help to satisfy your customers, coworkers, and managers.Perl has a strong history of automated tests. A very early release of Perl 1.0 included a comprehensive test suite, and it's only improved from there. Learning how Perl's test tools work and how to put them together to solve all sorts of previously intractable problems can make you a better programmer in general. Besides, it's easy to use the Perl tools described to handle all sorts of testing problems that you may encounter, even in other languages.Like all titles in O'Reilly's Developer's Notebook series, this "all lab, no lecture" book skips the boring prose and focuses instead on a series of exercises that speak to you instead of at you.Perl Testing: A Developer's Notebook will help you dive right in and: Write basic Perl tests with ease and interpret the results Apply special techniques and modules to improve your tests Bundle test suites along with projects Test databases and their data Test websites and web projects Use the "Test Anything Protocol" which tests projects written in languages other than PerlWith today's increased workloads and short development cycles, unit tests are more vital to building robust, high-quality software than ever before. Once mastered, these lessons will help you ensure low-level code correctness, reduce software development cycle time, and ease maintenance burdens.You don't have to be a die-hard free and open source software developer who lives, breathes, and dreams Perl to use this book. You just have to want to do your job a little bit better.
List of contents
The Developer's Notebook Series
Preface
Chapter 1: Beginning Testing
Chapter 2: Writing Tests
Chapter 3: Managing Tests
Chapter 4: Distributing Your Tests (and Code)
Chapter 5: Testing Untestable Code
Chapter 6: Testing Databases
Chapter 7: Testing Web Sites
Chapter 8: Unit Testing with Test::Class
Chapter 9: Testing Everything Else
Colophon
About the author
Ian Langworth (http://langworth.com/) has been writing Perlfor years and actively involved in the community since 2003.He has contributed a handful of modules to the CPAN, most ofwhich are Kwiki-related. He has spoken at Perl-relatedconferences as LISA and YAPC. Ian is also the authorsurprisingly widespread utility, Cadubi, which is packagedfor many free operating systems.Ian is currently studying Computer Science and CognitivePsychology at Northeastern University. Whilst pursuinga degree, he's participating in an volunteer systemsadministration group and working toward making higher codequality and robustness an easier goal to achieve.He currently resides in Boston, Massachusetts where heparticipates in the local Boston Perl Mongers group and livesprecariously close to Fenway Park.
chromatic is the technical editor of the O'Reilly Network, coveringopen source, Linux, development, and dynamic languages. He is also the author of the Extreme Programming Pocket Guide and Running Weblogs with Slash, as well as the editor of BSD Hacks and Gaming Hacks. He is the original author of Test::Builder, the foundation for most modern testing modules in Perl 5, and has contributed many of the tests for core Perl. He has given tutorials and presentations at several Perl conferences, including OSCON, and often writes for Perl.com, which he also edits. He lives just west of Portland, Oregon, with two cats, a creek in his backyard, and, as you may have guessed, several unfinished projects.
Summary
Good software testing can increase productivity, improve designs, raise quality, and make you more productive overall. This hands-on labs series teaches how Perl's test tools work and how to use them to create basic and complex tests and interpret the results. This notebook is helpful in reducing the software development cycle times.
