售价: ¥536.00 待定配送费
前翻 后翻
正在播放... 已暂停   您正在聆听的 Audible 音频版本的样品。
了解更多信息
查看全部 2 张图片

How to Break Software: A Practical Guide to Testing (英语) 平装 – 2002年5月19日

平均4 星
5 星
14
4 星
7
3 星
1
2 星
1
1 星
3
平均4 星 26条亚马逊美国的评论 us-flag |
| 天天低价·正品质优
|
分享
广告

显示所有 格式和版本 隐藏其他格式和版本
亚马逊价格
全新品最低价 非全新品最低价
平装
"请重试"
¥536.00
¥536.00
 

click to open popover

看过此商品后顾客买的其它商品?

无需Kindle设备,下载免费Kindle阅读软件,即可在您的手机、电脑及平板电脑上畅享阅读。

  • iPhone/iPad/Mac
  • Android手机或平板电脑

请输入您的手机号码,获取Kindle阅读软件的下载链接。



基本信息

  • 出版社: Pearson; 1 (2002年5月19日)
  • 平装: 208页
  • 语种: 英语
  • ISBN: 0201796198
  • 条形码: 9780201796193
  • 商品尺寸: 17.5 x 1.8 x 22.9 cm
  • 商品重量: 349 g
  • ASIN: 0201796198
  • 用户评分: 分享我的评价
  • 亚马逊热销商品排名: 图书商品里排第992,067名 (查看图书商品销售排行榜)
  • 您想告诉我们您发现了更低的价格?
    如果您是该商品的卖家,是否希望通过卖家支持建议更新

商品描述

作者简介

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

目录



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.

Annotated Glossary of Programming Terms.

Appendix A. Testing Exception and Error Cases Using Runtime Fault Injection.

Introduction.

A Mechanism for Runtime Fault Injection.

Fault Selection.

Conclusions.

Acknowledgments.

References.

Appendix B. Using HEAT: The Hostile Environment Application Tester.

Canned HEAT User Guide.

The Application Band.

The Monitor Band.

Fault Injection Bands and Their Functionality.

The Network Band.

Disk Storage.

Memory.

Appendix C. What is Software Testing? And Why is it so Hard?

Introduction.

The Software Testing Process.

Phase One: Modeling the Software's Environment.

Phase Two: Selecting Test Scenarios.

Phase Three: Running and Evaluating Test Scenarios.

Phase Four: Measuring Testing Progress.

Conclusion.

References.

The Software Testing Problem.

商品评论

在亚马逊中国上尚未有买家评论。
5 星
4 星
3 星
2 星
1 星

此商品在美国亚马逊上最有用的商品评论 (beta)

美国亚马逊: 平均4.0 星 26 条评论
1/1 人认为此评论有用
平均5.0 星 most thorough and organized book for beginners 2008年9月23日
评论者 Fauzia Lala - 已在美国亚马逊上发表
版本: 平装 已确认购买
Thsi book was recommended by two people working at Microsoft. One was a Test Lead in IIS team and another a Test Manager with the Games for Windows team. I thought that being the case it would be worth giving it a shot. Here are some of my observations:

1) This book is fast paced.

2) Every point is made succinctly and not blabbered on, so it keeps your interest througout.

3) Provides lots of examples to help relate. Many are errors in MS Word 2000, which also makes it interesting to read.

4) Covered many distinct types of approaches, so is very thorough and organized. Different types of testing, types of attack within each type of testing, how/what/when details of the attack is all listed. Nothing left out.

5) Aimed towards newbies to testing, but is a good quick refresher resource for those who have been into testing for a little bit.
8/9 人认为此评论有用
平均4.0 星 Great for Beginners 2005年4月16日
评论者 Einzige - 已在美国亚马逊上发表
版本: 平装 已确认购买
This is an awesome book for software testers with less than two years of experience. If that's you, then you'll definitely get a lot of value out of it. You should buy it without hesitation.

What it does well is provide a clear understanding of what it means to "think like a tester." I recommend also that QA managers give it to their greenest team members. They will undoubtedly become better testers as a result.

However, if you're someone who has been in QA for several years, all of these attacks are going to be obvious--and ones that you almost certainly will already consider a part of your regular testing repertoire.

Even still, it's fun reading about some of the extant bugs in shipping Microsoft products, with step-by-step instructions on how to make them happen. I also like the freeware that comes with it--it's limited in scope, but still quite useful for certain testing situations.
平均4.0 星 Four Stars 2015年11月19日
评论者 nmd - 已在美国亚马逊上发表
版本: 平装 已确认购买
Great book about software testing. Book was in promised condition from the seller
平均5.0 星 Great book for IT professionals 2012年7月3日
评论者 mschu - 已在美国亚马逊上发表
版本: 平装 已确认购买
This book is geared toward testers and how to properly test your software, but it should be required reading for software developers as they are usually the worst testers out there. I had the opportunity to take a one day course based on this book from the author is it was great.
3/3 人认为此评论有用
平均4.0 星 Great for beginner or intermediate 2007年4月23日
评论者 Caterina Pryde - 已在美国亚马逊上发表
版本: 平装 已确认购买
Great book covering orthodox and some unorthodox thoughts on testing methods and some specific guides. While the college trained tester or the person with many years of experience will probably find this too basic, it's still worth thumbing through for a new idea or two. The most common testing faults are missing common issues, such as testing for bad or negative input.