Testing Computer Software

ISBN-10: 0471358460

ISBN-13: 9780471358466

Edition: 2nd 1999 (Revised)

List price: $80.00
30 day, 100% satisfaction guarantee

If an item you ordered from TextbookRush does not meet your expectations due to an error on our part, simply fill out a return request and then return it by mail within 30 days of ordering it for a full refund of item cost.

Learn more about our returns policy


Without comprehensive testing, it is impossible to create successful and reliable software. This guide is for students, experienced programmers, project and test managers.
what's this?
Rush Rewards U
Members Receive:
You have reached 400 XP and carrot coins. That is the daily max!
Study Briefs

Limited time offer: Get the first one free! (?)

All the information you need in one place! Each Study Brief is a summary of one specific subject; facts, figures, and explanations to help you learn faster.

Add to cart
Study Briefs
Italian Grammar Online content $4.95 $1.99
Add to cart
Study Briefs
Portuguese Grammar Online content $4.95 $1.99
Add to cart
Study Briefs
Spanish Grammar Online content $4.95 $1.99
Add to cart
Study Briefs
German Grammar Online content $4.95 $1.99
Customers also bought

Book details

List price: $80.00
Edition: 2nd
Copyright year: 1999
Publisher: John Wiley & Sons, Incorporated
Publication date: 4/26/1999
Binding: Paperback
Pages: 496
Size: 7.50" wide x 9.25" long x 1.00" tall
Weight: 2.002

Notes on the book's structure and layout
An example test series
The first cycle of testing
The second cycle of testing
What will happen in later cycles of testing
The objectives and limits of testing
You can't test a program completely
The tester's objective: Program verification?
So, why test?
Test types and their place in the software development process
Overview of the software development stages
Planning stages
Testing during the planning stages
Design stages
Testing during the design stages
Glass box code testing is part of the coding stage
Regression testing
Black box testing
Software errors
What is a software error?
Categories of software errors
Reporting and analyzing bugs
Write Problem Reports immediately
Content of the Problem Report
Characteristics of the Problem Report
Analysis of a reproducible bug
Tactics for analyzing a reproducible bug
Making a bug reproducible
The problem tracking system
The prime objective of a problem tracking system
The tasks of the system
Problem tracking overview
The users of the tracking system
Mechanics of the database
Further thoughts on problem reporting
Test case design
Characteristics of a good test
Equivalence classes and boundary values
Visible state transitions
Race conditions and other time dependencies
Load testing
Error guessing
Function equivalence testing: automation, sensitivity analysis and random input
Regression testing: checking whether a bug fix worked
Regression testing: the standard battery of tests
Executing the tests
Testing printers (and other devices)
Some general issues in configuration testing
Printer testing
Localization testing
Was the base code changed?
Work with someone fluent in the language
Is the text independent from the code?
Translated text expands
Character sets
Text filters
Loading, saving, importing, and exporting high and low ASCII
Operating system language
Hot keys
Garbled in translation
Error message identifiers
Hyphenation rules
Spelling rules
Sorting rules
Uppercase and lowercase conversion
Underscoring rules
Sizes of paper
CPU's and video
Data formats and setup options
Rulers and measurements
Culture-bound graphics
Culture-bound output
European product compatibility
Memory availability
Do GUIs solve the problem?
Automated testing
Testing user manuals
Effective documentation
The documentation tester's objectives
How testing documentation contributes to software reliability
Become the technical editor
Working with the manual through its development stages
Online help
Testing tools
Fundamental tools
Automated acceptance and regression tests
Translucent-box testing
Test planning and test documentation
The overall objective of the test plan: product or tool?
Detailed objectives of test planning and documentation
What types of tests to cover in test planning documents
A strategy for developing components of test planning documents
Components of test planning documents
Documenting test materials
A closing thought
Managing Testing Projects and Groups
Tying it together
Software development tradeoffs
Software development models
Quality-related costs
The development time line
Product design
Fragments coded: first functionality
Almost alpha
User interface (UI) freeze
Final integrity testing
Project post-mortems
Legal consequences of defective software
Breach of contract
Torts: lawsuits involving fault
Whistle blowing
Managing a testing group
Managing a testing group
The role of the testing group
A test group is not an unmixed blessing
An alternative? Independent test agencies
Scheduling tips
Your staff
Appendix: common software errors
User interface errors
Error handling
Boundary-related errors
Calculation errors
Initial and later states
Control flow errors
Errors in handling or interpreting data
Race conditions
Load conditions
Source, version, and ID control
Testing errors
About the Authors
Free shipping on orders over $35*

*A minimum purchase of $35 is required. Shipping is provided via FedEx SmartPost® and FedEx Express Saver®. Average delivery time is 1 – 5 business days, but is not guaranteed in that timeframe. Also allow 1 - 2 days for processing. Free shipping is eligible only in the continental United States and excludes Hawaii, Alaska and Puerto Rico. FedEx service marks used by permission."Marketplace" orders are not eligible for free or discounted shipping.

Learn more about the TextbookRush Marketplace.