How to Break Software: A Practical Guide to Testing

3,68 valoración promedio
( 88 valoraciones por GoodReads )
 
9780201796193: How to Break Software: A Practical Guide to Testing
From the Publisher:

How to Break Software is a departure from conventional testing in which testers prepare a written test plan and then use it as a script when testing the software. The testing techniques in this book are as flexible as conventional testing is rigid. And flexibility is needed in software projects in which requirements can change, bugs can become features and schedule pressures often force plans to be reassessed. Software testing is not such an exact science that one can determine what to test in advance and then execute the plan and be done with it. Instead of a plan, intelligence, insight, experience and a "nose for where the bugs are hiding" should guide testers. This book helps testers develop this insight. The techniques presented in this book not only allow testers to go off-script, they encourage them to do so. Don't blindly follow a document that may be out of date and that was written before the product was even testable. Instead, use your head! Open your eyes! Think a little, test a little and then think a little more. This book does teach planning, but in an "on- the-fly while you are testing" way. It also encourages automation with many repetitive and complex tasks that require good tools (one such tool is shipped with this book on the companion CD). However, tools are never used as a replacement for intelligence. Testers do the thinking and use tools to collect data and help them explore applications more efficiently and effectively.

About the Author:

James A. Whittaker is a well-known speaker and consultant, as well as seasoned professor.

"Sobre este título" puede pertenecer a otra edición de este libro.

Los mejores resultados en AbeBooks

1.

Whittaker, James A.
Editorial: Pearson
ISBN 10: 0201796198 ISBN 13: 9780201796193
Nuevos PAPERBACK Cantidad: 1
Librería
Balkanika Online
(Woodinville, WA, Estados Unidos de America)
Valoración
[?]

Descripción Pearson. PAPERBACK. Estado de conservación: New. 0201796198 SEALED CD INCLUDED. Brand new book. Never used. Nice gift. Best buy. Shipped promptly and packaged carefully. Nº de ref. de la librería SKU8004133

Más información sobre esta librería | Hacer una pregunta a la librería

Comprar nuevo
EUR 25,66
Convertir moneda

Añadir al carrito

Gastos de envío: EUR 4,70
A Estados Unidos de America
Destinos, gastos y plazos de envío

2.

Whittaker, James A.
Editorial: Prentice Hall (2002)
ISBN 10: 0201796198 ISBN 13: 9780201796193
Nuevos Cantidad: > 20
Librería
Paperbackshop-US
(Commerce, GA, Estados Unidos de America)
Valoración
[?]

Descripción Prentice Hall, 2002. PAP. Estado de conservación: New. New Book. Shipped from UK within 10 to 14 business days. Established seller since 2000. Nº de ref. de la librería PJ-9780201796193

Más información sobre esta librería | Hacer una pregunta a la librería

Comprar nuevo
EUR 31,66
Convertir moneda

Añadir al carrito

Gastos de envío: EUR 3,75
A Estados Unidos de America
Destinos, gastos y plazos de envío

3.

Whittaker, James A.
Editorial: Pearson (2002)
ISBN 10: 0201796198 ISBN 13: 9780201796193
Nuevos Tapa blanda Cantidad: 1
Librería
Book Deals
(Lewiston, NY, Estados Unidos de America)
Valoración
[?]

Descripción Pearson, 2002. Estado de conservación: New. Brand New, Unread Copy in Perfect Condition. A+ Customer Service! Summary: Preface. Dedication. Chapter Summaries. I. INTRODUCTION. 1. A Fault Model to Guide Software Testing. The Purpose of Software Testing. Understanding Software Behavior. Understanding Software's Environment. The Human User. File System User. The Operating System User. The Software User. Understanding Software's Capabilities. Testing Input. Testing Output. Testing Data. Testing Competition. Summary and Conclusion. Exercises. References. II. USER INTERFACE ATTACKS. 2. Testing from the User Interface: Inputs and Outputs. Using the Fault Model to Guide Testing. Exploring the Input Domain. First Attack: Apply inputs that force all the error messages to occur. Second Attack: Apply inputs that force the software to establish default values. Third Attack: Explore allowable character sets and data types. Fourth Attack: Overflow input buffers. Fifth Attack: Find inputs that may interact and test various combinations of their values. Sixth Attack: Repeat the same input or series of inputs numerous times. Exploring Outputs. Seventh Attack: Force different outputs to be generated for each input. Eighth Attack: Force invalid outputs to be generated. Ninth Attack: Force properties of an output to change. Tenth Attack: Force the screen to refresh. Conclusion. Exercises. References. 3. Testing from the User Interface: Data and Computation. Testing Inside the Box. Exploring Stored Data. Eleventh Attack: Apply inputs using a variety of initial conditions. Twelfth Attack: Force a data structure to store too many/too few values. Thirteenth Attack: Investigate alternate ways to modify internal data constraints. Exploring Computation and Feature Interaction. Fifteenth Attack: Force a function to call itself recursively. Sixteenth Attack: Force computation results to be too large or too small. Seventeenth Attack: Find features that share data or interact poorly. Conclusion. Exercises. III. SYSTEM INTERFACE ATTACKS. 4. Testing from the File System Interface. Attacking Software from the File System Interface. Media-based Attacks. First Attack: Inject faults that simulate memory access problems. Second Attack: Inject faults that simulate network problems. Third Attack: Damage the media. File-based Attacks. Fourth Attack: Assign an invalid file name. Fifth Attack: Vary file access permissions. Sixth Attack: Vary/corrupt file contents. Exercises. 5. Testing from the Software/OS Interface. Attacking Software from Software Interfaces. Record-and-Simulate Attacks. Observe-and-Fail Attacks. Conclusion. Exercises. IV. CONCLUSION. 6. Some Parting Advice. You'll Never Know Everything. Bug Hunts. Friday Afternoon Bug Fests. Conclusion. References. APPENDICES. <BR. Nº de ref. de la librería ABE_book_new_0201796198

Más información sobre esta librería | Hacer una pregunta a la librería

Comprar nuevo
EUR 35,51
Convertir moneda

Añadir al carrito

Gastos de envío: GRATIS
A Estados Unidos de America
Destinos, gastos y plazos de envío

4.

Whittaker, James A.
Editorial: Prentice Hall
ISBN 10: 0201796198 ISBN 13: 9780201796193
Nuevos Cantidad: > 20
Librería
INDOO
(Avenel, NJ, Estados Unidos de America)
Valoración
[?]

Descripción Prentice Hall. Estado de conservación: New. Brand New. Nº de ref. de la librería 0201796198

Más información sobre esta librería | Hacer una pregunta a la librería

Comprar nuevo
EUR 32,94
Convertir moneda

Añadir al carrito

Gastos de envío: EUR 3,29
A Estados Unidos de America
Destinos, gastos y plazos de envío

5.

Whittaker, James A.
Editorial: Pearson
ISBN 10: 0201796198 ISBN 13: 9780201796193
Nuevos PAPERBACK Cantidad: 2
Librería
Movie Mars
(Indian Trail, NC, Estados Unidos de America)
Valoración
[?]

Descripción Pearson. PAPERBACK. Estado de conservación: New. 0201796198 Brand New Book. Ships from the United States. 30 Day Satisfaction Guarantee!. Nº de ref. de la librería 4703710

Más información sobre esta librería | Hacer una pregunta a la librería

Comprar nuevo
EUR 32,93
Convertir moneda

Añadir al carrito

Gastos de envío: EUR 3,75
A Estados Unidos de America
Destinos, gastos y plazos de envío

6.

Whittaker, James A.
Editorial: Pearson Education (US), United States (2002)
ISBN 10: 0201796198 ISBN 13: 9780201796193
Nuevos Paperback Cantidad: 1
Librería
The Book Depository
(London, Reino Unido)
Valoración
[?]

Descripción Pearson Education (US), United States, 2002. Paperback. Estado de conservación: New. 231 x 178 mm. Language: English . Brand New Book. How to Break Software is a departure from conventional testing in which testers prepare a written test plan and then use it as a script when testing the software. The testing techniques in this book are as flexible as conventional testing is rigid. And flexibility is needed in software projects in which requirements can change, bugs can become features and schedule pressures often force plans to be reassessed. Software testing is not such an exact science that one can determine what to test in advance and then execute the plan and be done with it. Instead of a plan, intelligence, insight, experience and a nose for where the bugs are hiding should guide testers. This book helps testers develop this insight. The techniques presented in this book not only allow testers to go off-script, they encourage them to do so. Don t blindly follow a document that may be out of date and that was written before the product was even testable. Instead, use your head! Open your eyes! Think a little, test a little and then think a little more. This book does teach planning, but in an on- the-fly while you are testing way. It also encourages automation with many repetitive and complex tasks that require good tools (one such tool is shipped with this book on the companion CD). However, tools are never used as a replacement for intelligence. Testers do the thinking and use tools to collect data and help them explore applications more efficiently and effectively. Nº de ref. de la librería AAC9780201796193

Más información sobre esta librería | Hacer una pregunta a la librería

Comprar nuevo
EUR 37,19
Convertir moneda

Añadir al carrito

Gastos de envío: GRATIS
De Reino Unido a Estados Unidos de America
Destinos, gastos y plazos de envío

7.

Whittaker, James A.
Editorial: Pearson Education (US), United States (2002)
ISBN 10: 0201796198 ISBN 13: 9780201796193
Nuevos Paperback Cantidad: 1
Librería
The Book Depository US
(London, Reino Unido)
Valoración
[?]

Descripción Pearson Education (US), United States, 2002. Paperback. Estado de conservación: New. 231 x 178 mm. Language: English . Brand New Book. How to Break Software is a departure from conventional testing in which testers prepare a written test plan and then use it as a script when testing the software. The testing techniques in this book are as flexible as conventional testing is rigid. And flexibility is needed in software projects in which requirements can change, bugs can become features and schedule pressures often force plans to be reassessed. Software testing is not such an exact science that one can determine what to test in advance and then execute the plan and be done with it. Instead of a plan, intelligence, insight, experience and a nose for where the bugs are hiding should guide testers. This book helps testers develop this insight. The techniques presented in this book not only allow testers to go off-script, they encourage them to do so. Don t blindly follow a document that may be out of date and that was written before the product was even testable. Instead, use your head! Open your eyes! Think a little, test a little and then think a little more. This book does teach planning, but in an on- the-fly while you are testing way. It also encourages automation with many repetitive and complex tasks that require good tools (one such tool is shipped with this book on the companion CD). However, tools are never used as a replacement for intelligence. Testers do the thinking and use tools to collect data and help them explore applications more efficiently and effectively. Nº de ref. de la librería AAC9780201796193

Más información sobre esta librería | Hacer una pregunta a la librería

Comprar nuevo
EUR 37,91
Convertir moneda

Añadir al carrito

Gastos de envío: GRATIS
De Reino Unido a Estados Unidos de America
Destinos, gastos y plazos de envío

8.

Whittaker, James A.
Editorial: Addison-Wesley (2002)
ISBN 10: 0201796198 ISBN 13: 9780201796193
Nuevos Paperback Cantidad: 1
Librería
Ergodebooks
(RICHMOND, TX, Estados Unidos de America)
Valoración
[?]

Descripción Addison-Wesley, 2002. Paperback. Estado de conservación: New. Nº de ref. de la librería DADAX0201796198

Más información sobre esta librería | Hacer una pregunta a la librería

Comprar nuevo
EUR 36,24
Convertir moneda

Añadir al carrito

Gastos de envío: EUR 3,75
A Estados Unidos de America
Destinos, gastos y plazos de envío

9.

Whittaker, James A.
Editorial: Pearson (2002)
ISBN 10: 0201796198 ISBN 13: 9780201796193
Nuevos Paperback Cantidad: 1
Librería
Irish Booksellers
(Rumford, ME, Estados Unidos de America)
Valoración
[?]

Descripción Pearson, 2002. Paperback. Estado de conservación: New. book. Nº de ref. de la librería 0201796198

Más información sobre esta librería | Hacer una pregunta a la librería

Comprar nuevo
EUR 40,31
Convertir moneda

Añadir al carrito

Gastos de envío: GRATIS
A Estados Unidos de America
Destinos, gastos y plazos de envío

10.

Whittaker, James A.
Editorial: Pearson Education (US)
ISBN 10: 0201796198 ISBN 13: 9780201796193
Nuevos Paperback Cantidad: 2
Librería
THE SAINT BOOKSTORE
(Southport, Reino Unido)
Valoración
[?]

Descripción Pearson Education (US). Paperback. Estado de conservación: new. BRAND NEW, How to Break Software: A Practical Guide to Testing, James A. Whittaker, How to Break Software is a departure from conventional testing in which testers prepare a written test plan and then use it as a script when testing the software. The testing techniques in this book are as flexible as conventional testing is rigid. And flexibility is needed in software projects in which requirements can change, bugs can become features and schedule pressures often force plans to be reassessed. Software testing is not such an exact science that one can determine what to test in advance and then execute the plan and be done with it. Instead of a plan, intelligence, insight, experience and a "nose for where the bugs are hiding" should guide testers. This book helps testers develop this insight. The techniques presented in this book not only allow testers to go off-script, they encourage them to do so. Don't blindly follow a document that may be out of date and that was written before the product was even testable. Instead, use your head! Open your eyes! Think a little, test a little and then think a little more. This book does teach planning, but in an "on- the-fly while you are testing" way. It also encourages automation with many repetitive and complex tasks that require good tools (one such tool is shipped with this book on the companion CD). However, tools are never used as a replacement for intelligence. Testers do the thinking and use tools to collect data and help them explore applications more efficiently and effectively. Nº de ref. de la librería B9780201796193

Más información sobre esta librería | Hacer una pregunta a la librería

Comprar nuevo
EUR 35,05
Convertir moneda

Añadir al carrito

Gastos de envío: EUR 6,73
De Reino Unido a Estados Unidos de America
Destinos, gastos y plazos de envío

Existen otras copia(s) de este libro

Ver todos los resultados de su búsqueda