Testing computer software

"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 product...

Full description

Saved in:
Bibliographic Details
Main Author: Kaner, Cem.
Other Authors: Falk, Jack L., 1950-, Nguyen, Hung Quoc.
Format: eBook
Language: English
Published: New York : Wiley, ©1999.
Edition: 2nd ed.
Subjects:
Computer software > Testing.
elektronické knihy
electronic books
ISBN: 9781523118359
1523118350
0471358460
9780471358466
Physical Description: 1 online resource (xv, 480 pages) : illustrations, form

Cover

Table of contents

LEADER 07010cam a2200529 a 4500
001 kn-ocn894785628
003 OCoLC
005 20240717213016.0
006 m o d
007 cr cn|||||||||
008 141107r19991993nyuak ob 001 0 eng d
040 |a OCLCE  |b eng  |e pn  |c OCLCE  |d UMI  |d DEBSZ  |d OCLCQ  |d OCLCO  |d OCLCQ  |d CEF  |d OCLCA  |d KNOVL  |d OCLCA  |d OCLCQ  |d OCLCO  |d OCLCQ  |d OCLCO  |d OCLCL 
020 |a 9781523118359  |q (electronic bk.) 
020 |a 1523118350  |q (electronic bk.) 
020 |z 0471358460  |q (pbk. ;  |q acid-free paper) 
020 |z 9780471358466  |q (pbk. ;  |q acid-free paper) 
035 |a (OCoLC)894785628  |z (OCoLC)846957956  |z (OCoLC)1044318927  |z (OCoLC)1056350941  |z (OCoLC)1060899289  |z (OCoLC)1075514642  |z (OCoLC)1103537596  |z (OCoLC)1420710283 
042 |a dlr 
100 1 |a Kaner, Cem. 
245 1 0 |a Testing computer software /  |c Cem Kaner, Jack Falk, Hung Quoc Nguyen. 
250 |a 2nd ed. 
260 |a New York :  |b Wiley,  |c ©1999. 
300 |a 1 online resource (xv, 480 pages) :  |b illustrations, form 
336 |a text  |b txt  |2 rdacontent 
337 |a computer  |b c  |2 rdamedia 
338 |a online resource  |b cr  |2 rdacarrier 
504 |a Includes bibliographical references (pages 437-450) and index. 
506 |a Plný text je dostupný pouze z IP adres počítačů Univerzity Tomáše Bati ve Zlíně nebo vzdáleným přístupem pro zaměstnance a studenty 
520 1 |a "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. Book jacket."--Jacket 
505 0 0 |t Notes on the book's structure and layout --  |t Fundamentals --  |t An example test series --  |t The first cycle of testing --  |t The second cycle of testing --  |t What will happen in later cycles of testing --  |t The objectives and limits of testing --  |t You can't test a program completely --  |t The tester's objective: Program verification? --  |t So, why test? --  |t Test types and their place in the software development process --  |t Overview of the software development stages --  |t Planning stages. 
505 8 |t Testing during the planning stages --  |t Design stages --  |t Testing during the design stages --  |t Glass box code testing is part of the coding stage --  |t Regression testing --  |t Black box testing --  |t Maintenance --  |t Software errors --  |t Quality --  |t What is a software error? --  |t Categories of software errors --  |t Reporting and analyzing bugs --  |t Write Problem Reports immediately --  |t Content of the Problem Report --  |t Characteristics of the Problem Report --  |t Analysis of a reproducible bug. 
505 8 |t Tactics for analyzing a reproducible bug --  |t Making a bug reproducible --  |t The problem tracking system --  |t The prime objective of a problem tracking system --  |t The tasks of the system --  |t Problem tracking overview --  |t The users of the tracking system --  |t Mechanics of the database --  |t Further thoughts on problem reporting --  |t Test case design --  |t Characteristics of a good test --  |t Equivalence classes and boundary values --  |t Visible state transitions. 
505 8 |t Race conditions and other time dependencies --  |t Load testing --  |t Error guessing --  |t Function equivalence testing: automation, sensitivity analysis & random input --  |t Regression testing: checking whether a bug fix worked --  |t Regression testing: the standard battery of tests --  |t Executing the tests --  |t Testing printers (and other devices) --  |t Some general issues in configuration testing --  |t Printer testing --  |t Localization testing --  |t Was the base code changed?. 
505 8 |t Work with someone fluent in the language --  |t Is the text independent from the code? --  |t Translated text expands --  |t Character sets --  |t Keyboards --  |t Text filters --  |t Loading, saving, importing, and exporting high and low ASCII --  |t Operating system language --  |t Hot keys --  |t Garbled in translation --  |t Error message identifiers --  |t Hyphenation rules --  |t Spelling rules --  |t Sorting rules --  |t Uppercase and lowercase conversion --  |t Underscoring rules --  |t Printers --  |t Sizes of paper. 
505 8 |t CPU's and video --  |t Rodents --  |t Data formats and setup options --  |t Rulers and measurements --  |t Culture-bound graphics --  |t Culture-bound output --  |t European product compatibility --  |t Memory availability --  |t Do GUIs solve the problem? --  |t Automated testing --  |t Testing user manuals --  |t Effective documentation --  |t The documentation tester's objectives --  |t How testing documentation contributes to software reliability --  |t Become the technical editor. 
505 8 |t Working with the manual through its development stages --  |t Online help --  |t Testing tools --  |t Fundamental tools --  |t Automated acceptance and regression tests --  |t Standards --  |t Translucent-box testing --  |t Test planning and test documentation --  |t The overall objective of the test plan: product or tool? --  |t Detailed objectives of test planning and documentation --  |t What types of tests to cover in test planning documents --  |t A strategy for developing components of test planning documents. 
505 8 |t Components of test planning documents --  |t Documenting test materials --  |t A closing thought --  |t Managing Testing Projects and Groups --  |t Tying it together --  |t Software development tradeoffs --  |t Software development models --  |t Quality-related costs --  |t The development time line --  |t Product design --  |t Fragments coded: first functionality --  |t Almost alpha --  |t Alpha --  |t Pre-beta --  |t Beta --  |t User interface (UI) freeze --  |t Pre-final --  |t Final integrity testing --  |t Release --  |t Project post-mortems. 
505 8 |t Legal consequences of defective software --  |t Breach of contract --  |t Torts: lawsuits involving fault --  |t Whistle blowing --  |t Managing a testing group --  |t Managing a testing group --  |t The role of the testing group --  |t A test group is not an unmixed blessing --  |t An alternative? Independent test agencies --  |t Scheduling tips --  |t Your staff --  |t Appendix: common software errors --  |t User interface errors --  |t Error handling --  |t Boundary-related errors --  |t Calculation errors. 
505 8 |t Initial and later states --  |t Control flow errors --  |t Errors in handling or interpreting data --  |t Race conditions --  |t Load conditions --  |t Hardware --  |t Source, version, and ID control --  |t Testing errors. 
590 |a Knovel  |b Knovel (All titles) 
650 0 |a Computer software  |x Testing. 
655 7 |a elektronické knihy  |7 fd186907  |2 czenas 
655 9 |a electronic books  |2 eczenas 
700 1 |a Falk, Jack L.,  |d 1950-  |1 https://id.oclc.org/worldcat/entity/E39PCjFcv8bq9m4qRdCM9F7Rw3 
700 1 |a Nguyen, Hung Quoc. 
776 0 8 |i Print version:  |a Kaner, Cem.  |t Testing computer software.  |b 2nd ed.  |d New York : Wiley, ©1999  |w (OCoLC)42078224 
856 4 0 |u https://proxy.k.utb.cz/login?url=https://app.knovel.com/hotlink/toc/id:kpTCSE0003/testing-computer-software?kpromoter=marc  |y Full text 

Similar Items