Details

Subject(s)

• Perl (Computer program language) [Browse]

Related name

• Chromatic [Browse]

Summary note

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 impr

Notes

Includes index.

Source of description

Description based on online resource; title from PDF title page (ebrary, viewed October 8, 2013).

Language note

English

Contents

• Contents; The Developer's Notebook Series; Notebooks Are...; Notebooks Aren't...; Organization; Preface; What This Book Covers; Conventions Used in This Book; Using Code Examples; Safari Enabled; Comments and Questions; Acknowledgments; Ian Langworth; chromatic; Chapter 1: Beginning Testing; Installing Test Modules; How do I do that?; Through the CPAN shell; Through PPM; By hand; What about...; Running Tests; How do I do that?; What just happened?; What about...; Interpreting Test Results; How do I do that?; What just happened?; What about...; Writing Your First Test; How do I do that?
• What just happened?What about...; Loading Modules; How do I do that?; What just happened?; What about...; Improving Test Comparisons; How do I do that?; What just happened?; What about...; Chapter 2: Writing Tests; Skipping Tests; How do I do that?; What just happened?; Skipping All Tests; How do I do that?; What just happened?; Marking Tests as TODO; How do I do that?; What just happened?; What about...; Simple Data Structure Equality; How do I do that?; What just happened?; What about...; Data Composition; How do I do that?; What just happened?; What about...; Where to learn more
• Testing WarningsHow do I do that?; What just happened?; What about...; Testing Exceptions; How do I do that?; What just happened?; What about...; Chapter 3: Managing Tests; Organizing Tests; How do I do that?; What just happened?; What about...; Checking Your Coverage; How do I do that?; What just happened?; What about...; Writing a Testing Library; How do I do that?; What just happened?; What about...; Testing a Testing Library; How do I do that?; What just happened?; What about...; Writing a Testing Harness; How do I do that?; What just happened?; Testing Across the Network
• How do I do that?What just happened?; What about...; Automating Test Runs; How do I do that?; What just happened?; What about...; Chapter 4: Distributing Your Tests (and Code); Testing POD Files; How do I do that?; What just happened?; What about...; Testing Documentation Coverage; How do I do that?; What just happened?; What about...; Distribution Signatures; How do I do that?; What just happened?; Testing Entire Distributions; How do I do that?; What just happened?; What about...; Letting the User Decide; How do I do that?; What just happened?; Letting the User Decide (Continued)
• How do I do that?What just happened?; Bundling Tests with Modules; How do I do that?; What just happened?; What about?; Collecting Test Results; How do I do that?; What just happened?; What about...; Validating Kwalitee; How do I do that?; What just happened?; What about...; Chapter 5: Testing Untestable Code; Overriding Built-ins; How do I do that?; What just happened?; What about...; Mocking Modules; How do I do that?; What just happened?; What about...; Mocking Objects; How do I do that?; What just happened?; What about...; Partially Mocking Objects; How do I do that?; What just happened?
• What about...

Show 3 more Contents items

Other format(s)

Available also in a print edition.

ISBN

• 1-4493-1308-6
• 1-4493-1367-1

OCLC

74459496

Statement on language in description

Princeton University Library aims to describe library materials in a manner that is respectful to the individuals and communities who create, use, and are represented in the collections we manage. Read more...