Publisher: O'Reilly Media Released: July 2005 Pages: 208
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. And that'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 Perl
With 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. |
-
Chapter 1 Beginning Testing -
Installing Test Modules -
Running Tests -
Interpreting Test Results -
Writing Your First Test -
Loading Modules -
Improving Test Comparisons -
Chapter 2 Writing Tests -
Skipping Tests -
Skipping All Tests -
Marking Tests as TODO -
Simple Data Structure Equality -
Data Composition -
Testing Warnings -
Testing Exceptions -
Chapter 3 Managing Tests -
Organizing Tests -
Checking Your Coverage -
Writing a Testing Library -
Testing a Testing Library -
Writing a Testing Harness -
Testing Across the Network -
Automating Test Runs -
Chapter 4 Distributing Your Tests (and Code) -
Testing POD Files -
Testing Documentation Coverage -
Distribution Signatures -
Testing Entire Distributions -
Letting the User Decide -
Letting the User Decide (Continued) -
Bundling Tests with Modules -
Collecting Test Results -
Validating Kwalitee -
Chapter 5 Testing Untestable Code -
Overriding Built-ins -
Mocking Modules -
Mocking Objects -
Partially Mocking Objects -
Overriding Live Code -
Overriding Operators Everywhere -
Chapter 6 Testing Databases -
Shipping Test Databases -
Testing Database Data -
Using Temporary Databases -
Mocking Databases -
Chapter 7 Testing Web Sites -
Testing Your Backend -
Testing Your Frontend -
Record and Play Back Browsing Sessions -
Testing the Validity of HTML -
Running Your Own Apache Server -
Testing with Apache-Test -
Distributing Modules with Apache-Test -
Chapter 8 Unit Testing with Test::Class -
Writing Test Cases -
Creating Test Fixtures -
Inheriting Tests -
Skipping Tests with Test::Class -
Marking Tests as TODO with Test::Class -
Chapter 9 Testing Everything Else -
Writing Testable Programs -
Testing Programs -
Testing Interactive Programs -
Testing Shared Libraries -
Colophon |
- Title:
- Perl Testing: A Developer's Notebook
- By:
- Ian Langworth, Chromatic
- Publisher:
- O'Reilly Media
- Formats:
-
- Print
- Ebook
- Safari Books Online
- Print:
- July 2005
- Ebook:
- July 2011
- Pages:
- 208
- Print ISBN:
- 978-0-596-10092-6
- | ISBN 10:
- 0-596-10092-2
- Ebook ISBN:
- 978-1-4493-8648-1
- | ISBN 10:
- 1-4493-8648-2
|
-
Ian Langworth 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. View Ian Langworth's full profile page. -
Chromatic 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. View Chromatic's full profile page. |
Colophon The Developer's Notebook series is modeled on the tradition of laboratory notebooks. Laboratory notebooks are an invaluable tool for researchers and their successors.The purpose of a laboratory notebook is to facilitate the recording of data and conclusions as the work is being conducted, creating a faithful and immediate history. The notebook begins with a title page that includes the owner's name and the subject of research. The pages of the notebook should be numbered and prefaced with a table of contents. Entries must be clear, easy to read, and accurately dated; they should use simple, direct language to indicate the name of the experiment and the steps taken. Calculations are written out carefully and relevant thoughts and ideas recorded. Each experiment is introduced and summarized as it is added to the notebook. The goal is to produce comprehensive, clearly organized notes that can be used as a reference. Careful documentation creates a valuable record and provides a practical guide for future developers. |
|
Description
|
Table of Contents
|
Product Details
|
About the Author
|
Colophon
|
 |
|
 |
|
|
|
Recommended for You
|
Recently Viewed
|
 |
|
By Josh Clark
June 2010
Ebook: $31.99
Print & Ebook: $43.99
Print: $39.99
By James Murty
March 2008
Ebook: $39.99
Print & Ebook: $54.99
Print: $49.99
By Brian McConnell
March 2001
|
Customer Reviews
5/24/2009 (2 of 2 customers found this review helpful) By Kiffin Gish from Undisclosed
|
|
|