+612 9045 4394
 
CHECKOUT
Testing Computer Software - Cem Kaner

Paperback

Published: 22nd April 1999
Ships: 15 business days
15 business days
RRP $195.00
$101.75
48%
OFF
or 4 easy payments of $25.44 with Learn more

This book will teach you how to test computer software under real-world conditions. The authors have all been test managers and software development managers at well-known Silicon Valley software companies. Successful consumer software companies have learned how to produce high-quality products under tight time and budget constraints. The book explains the testing side of that success.<br> <br> Who this book is for:<br> * Testers and Test Managers<br> * Project Managers-Understand the timeline, depth of investigation, and quality of communication to hold testers accountable for.<br> * Programmers-Gain insight into the sources of errors in your code, understand what tests your work will have to pass, and why testers do the things they do.<br> * Students-Train for an entry-level position in software development.<br> <br> What you will learn:<br> * How to find important bugs quickly<br> * How to describe software errors clearly<br> * How to create a testing plan with a minimum of paperwork<br> * How to design and use a bug-tracking system<br> * Where testing fits in the product development process<br> * How to test products that will be translated into other languages<br> * How to test for compatibility with devices, such as printers<br> * What laws apply to software quality

"Deep insight and a great deal of experience is contained in this book" (Database & Network Journal, Vol 30/5 2000)

Prefacep. xiii
Notes on the book's structure and layoutp. xvii
Acknowledgmentsp. xxi
Fundamentals
An example test seriesp. 1
The first cycle of testingp. 1
The second cycle of testingp. 11
What will happen in later cycles of testingp. 16
The objectives and limits of testingp. 17
You can't test a program completelyp. 17
The tester's objective: Program verification?p. 23
So, why test?p. 25
Test types and their place in the software development processp. 27
Overview of the software development stagesp. 30
Planning stagesp. 32
Testing during the planning stagesp. 33
Design stagesp. 35
Testing during the design stagesp. 39
Glass box code testing is part of the coding stagep. 41
Regression testingp. 49
Black box testingp. 50
Maintenancep. 57
Software errorsp. 59
Qualityp. 59
What is a software error?p. 60
Categories of software errorsp. 60
Reporting and analyzing bugsp. 65
Write Problem Reports immediatelyp. 66
Content of the Problem Reportp. 66
Characteristics of the Problem Reportp. 74
Analysis of a reproducible bugp. 76
Tactics for analyzing a reproducible bugp. 79
Making a bug reproduciblep. 82
The problem tracking systemp. 87
The prime objective of a problem tracking systemp. 90
The tasks of the systemp. 90
Problem tracking overviewp. 90
The users of the tracking systemp. 97
Mechanics of the databasep. 106
Further thoughts on problem reportingp. 115
Glossaryp. 121
Test case designp. 123
Characteristics of a good testp. 124
Equivalence classes and boundary valuesp. 125
Visible state transitionsp. 132
Race conditions and other time dependenciesp. 133
Load testingp. 134
Error guessingp. 135
Function equivalence testing: automation, sensitivity analysis and random inputp. 135
Regression testing: checking whether a bug fix workedp. 139
Regression testing: the standard battery of testsp. 140
Executing the testsp. 141
Testing printers (and other devices)p. 143
Some general issues in configuration testingp. 144
Printer testingp. 146
Localization testingp. 169
Was the base code changed?p. 170
Work with someone fluent in the languagep. 170
Is the text independent from the code?p. 171
Translated text expandsp. 171
Character setsp. 171
Keyboardsp. 172
Text filtersp. 172
Loading, saving, importing, and exporting high and low ASCIIp. 173
Operating system languagep. 173
Hot keysp. 173
Garbled in translationp. 173
Error message identifiersp. 174
Hyphenation rulesp. 174
Spelling rulesp. 174
Sorting rulesp. 174
Uppercase and lowercase conversionp. 174
Underscoring rulesp. 174
Printersp. 175
Sizes of paperp. 175
CPU's and videop. 175
Rodentsp. 175
Data formats and setup optionsp. 175
Rulers and measurementsp. 176
Culture-bound graphicsp. 176
Culture-bound outputp. 176
European product compatibilityp. 176
Memory availabilityp. 176
Do GUIs solve the problem?p. 177
Automated testingp. 177
Testing user manualsp. 179
Effective documentationp. 179
The documentation tester's objectivesp. 180
How testing documentation contributes to software reliabilityp. 181
Become the technical editorp. 182
Working with the manual through its development stagesp. 183
Online helpp. 188
Testing toolsp. 189
Fundamental toolsp. 189
Automated acceptance and regression testsp. 191
Standardsp. 197
Translucent-box testingp. 200
Test planning and test documentationp. 203
The overall objective of the test plan: product or tool?p. 204
Detailed objectives of test planning and documentationp. 205
What types of tests to cover in test planning documentsp. 210
A strategy for developing components of test planning documentsp. 213
Components of test planning documentsp. 217
Documenting test materialsp. 242
A closing thoughtp. 253
Managing Testing Projects and Groups
Tying it togetherp. 255
Software development tradeoffsp. 257
Software development modelsp. 258
Quality-related costsp. 264
The development time linep. 266
Product designp. 267
Fragments coded: first functionalityp. 274
Almost alphap. 275
Alphap. 277
Pre-betap. 286
Betap. 286
User interface (UI) freezep. 293
Pre-finalp. 295
Final integrity testingp. 299
Releasep. 301
Project post-mortemsp. 301
Legal consequences of defective softwarep. 303
Breach of contractp. 305
Torts: lawsuits involving faultp. 317
Whistle blowingp. 340
Managing a testing groupp. 343
Managing a testing groupp. 344
The role of the testing groupp. 345
A test group is not an unmixed blessingp. 349
An alternative? Independent test agenciesp. 350
Scheduling tipsp. 352
Your staffp. 359
Appendix: common software errorsp. 363
User interface errorsp. 375
Error handlingp. 396
Boundary-related errorsp. 399
Calculation errorsp. 401
Initial and later statesp. 403
Control flow errorsp. 406
Errors in handling or interpreting datap. 416
Race conditionsp. 421
Load conditionsp. 423
Hardwarep. 427
Source, version, and ID controlp. 430
Testing errorsp. 432
Referencesp. 437
Indexp. 451
About the Authorsp. 480
Table of Contents provided by Syndetics. All Rights Reserved.

ISBN: 9780471358466
ISBN-10: 0471358460
Audience: Professional
Format: Paperback
Language: English
Number Of Pages: 496
Published: 22nd April 1999
Publisher: John Wiley and Sons Ltd
Country of Publication: US
Dimensions (cm): 23.5 x 18.7  x 2.6
Weight (kg): 0.73
Edition Number: 2
Edition Type: Revised