How to Break Software : A Practical Guide to Testing (PAP/CDR)

個数:

How to Break Software : A Practical Guide to Testing (PAP/CDR)

  • 在庫がございません。海外の書籍取次会社を通じて出版社等からお取り寄せいたします。
    通常6~9週間ほどで発送の見込みですが、商品によってはさらに時間がかかることもございます。
    重要ご説明事項
    1. 納期遅延や、ご入手不能となる場合がございます。
    2. 複数冊ご注文の場合、分割発送となる場合がございます。
    3. 美品のご指定は承りかねます。
  • 製本 Paperback:紙装版/ペーパーバック版
  • 言語 ENG,ENG
  • 商品コード 9780201796193
  • DDC分類 005.14

Full Description


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.

Table of Contents

PART 1: INTRODUCTION
A Fault Model to Guide Software Testing
PART 2: USER INTERFACE ATTACKS
Testing from the User Interface: Inputs and
Outputs
Testing from the User Interface: Data and
Computation
PART 3: SYSTEM INTERFACE ATTACKS
Testing from the File System Interface
Testing from the Software/OS Interface
PART 4: CONCLUSION
Some Parting Advice
APPENDIXES
Annotated Glossary of Programming Terms
Appendix A--Runtime Fault Injection
Appendix B--Using HEAT: The Hostile
Environment Application Tester
Appendix C--What is Software Testing? And
Why is it So Hard?