The art of software testing /
Glenford J. Myers.
New York : Wiley, c1979.
xi, 177 p. : ill.
More Details
New York : Wiley, c1979.
general note
"A Wiley-Interscience publication."
catalogue key
Includes bibliographies and index.
A Look Inside
About the Author
Author Affiliation
Glenford J. Myers is currently Director of Spectrum Signals Tom Badgett is Chief Information Officer for IdleAire Technologies Corporation Todd M. Thomas is a professional software developer and database administrator with over nine years of experience. His career has exposed him to all sizes of software projects for both the private and government sectors. He has also authored Java Data Access, a book on how to use Java technology to leverage enterprise data stores Corey Sandler is President of Word Association
Main Description
Provides a practical rather than theoretical discussion of the purpose and nature of software testing. Emphasizes methodologies for the design of effective test cases. Comprehensively covers psychological and economic principles, managerial aspects of testing, test tools, high-order testing, code inspections, and debugging. Extensive bibliography. Programmers at all levels, and programming students, will find this reference work indispensible.
Table of Contents
List of Figures and Tablesp. ix
Prefacep. xi
Introductionp. xiii
A Self-Assessment Testp. 1
The Psychology and Economics of Program Testingp. 5
The Psychology of Testingp. 5
The Economics of Testingp. 9
Black-Box Testingp. 9
White-Box Testingp. 11
Software Testing Principlesp. 14
Summaryp. 20
Program Inspections, Walkthroughs, and Reviewsp. 21
Inspections and Walkthroughsp. 22
Code Inspectionsp. 24
An Error Checklist for Inspectionsp. 27
Data Reference Errorsp. 27
Data-Declaration Errorsp. 29
Computation Errorsp. 30
Comparison Errorsp. 31
Control-Flow Errorsp. 32
Interface Errorsp. 34
Input/Output Errorsp. 35
Other Checksp. 38
Walkthroughsp. 38
Desk Checkingp. 40
Peer Ratingsp. 40
Summaryp. 42
Test-Case Designp. 43
White-Box Testingp. 44
Logic-Coverage Testingp. 44
Equivalence Partitioningp. 52
An Examplep. 56
Boundary-Value Analysisp. 59
Cause-Effect Graphingp. 65
Error Guessingp. 88
The Strategyp. 90
Module (Unit) Testingp. 91
Test-Case Designp. 92
Incremental Testingp. 105
Top-down versus Bottom-up Testingp. 109
Top-down Testingp. 110
Bottom-up Testingp. 116
A Comparisonp. 118
Performing the Testp. 120
Higher-Order Testingp. 123
Function Testingp. 129
System Testingp. 130
Facility Testingp. 133
Volume Testingp. 133
Stress Testingp. 134
Usability Testingp. 135
Security Testingp. 137
Performance Testingp. 137
Storage Testingp. 138
Configuration Testingp. 138
Compatibility/Configuration/Conversion Testingp. 138
Installability Testingp. 139
Reliability Testingp. 139
Recovery Testingp. 141
Serviceability Testingp. 142
Documentation Testingp. 142
Procedure Testingp. 142
Performing the System Testp. 143
Acceptance Testingp. 144
Installation Testingp. 144
Test Planning and Controlp. 145
Test Completion Criteriap. 148
The Independent Test Agencyp. 155
Debuggingp. 157
Debugging by Brute Forcep. 158
Debugging by Inductionp. 160
Debugging by Deductionp. 164
Debugging by Backtrackingp. 168
Debugging by Testingp. 169
Debugging Principlesp. 170
Error-Locating Principlesp. 170
Error-Repairing Techniquesp. 171
Error Analysisp. 173
Extreme Testingp. 177
Extreme Programming Basicsp. 178
Extreme Testing: The Conceptsp. 183
Extreme Unit Testingp. 183
Acceptance Testingp. 185
Extreme Testing Appliedp. 186
Test-Case Designp. 186
Test Driver and Applicationp. 189
Summaryp. 191
Testing Internet Applicationsp. 193
Basic E-commerce Architecturep. 194
Testing Challengesp. 196
Testing Strategiesp. 200
Presentation Layer Testingp. 202
Business Layer Testingp. 205
Data Layer Testingp. 208
Sample Extreme Testing Applicationp. 213
Prime Numbers Less Than 1,000p. 221
Glossaryp. 223
Indexp. 227
Table of Contents provided by Rittenhouse. All Rights Reserved.

This information is provided by a service that aggregates data from review sources and other sources that are often consulted by libraries, and readers. The University does not edit this information and merely includes it as a convenience for users. It does not warrant that reviews are accurate. As with any review users should approach reviews critically and where deemed necessary should consult multiple review sources. Any concerns or questions about particular reviews should be directed to the reviewer and/or publisher.

  link to old catalogue

Report a problem