第四版《软件测试：匠人之道》：模型驱动的全面指南

5星 · 超过95%的资源需积分: 33 119 浏览量更新于2024-07-22 1 收藏 3.17MB PDF 举报

"《软件测试：工匠之道第四版》是一本由Paul C. Jorgensen编著的专业软件测试指南，该书在2013年10月18日由Auerbach Publications出版，适合英语阅读。本书是前三版的更新和重组，特别关注模型驱动测试，涵盖了代码（结构）和规范（功能）测试的各个方面，从单元测试扩展到集成和系统测试，深入探讨了软件测试的各个层次。第四版的特点包括强化技术审查，附录中提供了样本用例技术审查所需的完整文档集。书中引入了一种创新方法，将早期版本中的事件驱动Petri网与统一建模语言（UML）中的“泳道”概念相结合，为系统-of-systems中的四个交互层次提供模型驱动的测试策略。此外，作者还介绍了模型驱动开发，并解释了如何在模型驱动开发环境中进行测试。新章节涵盖了敏捷编程环境下的软件测试方法，重新审视了全对测试，并详细阐述了软件测试的四个上下文。书中全面修订和更新了内容，确保读者了解软件测试领域的最新技术动态。内容覆盖广泛，包括单元测试、边界值测试、等价类测试、决策表测试、路径测试、数据流测试、模型基础测试、系统测试、对象导向测试、软件复杂性分析、系统-of-systems模型测试、探索性测试、测试驱动开发、全对测试评估以及软件技术评审等多个主题。《软件测试：工匠之道第四版》不仅针对软件测试人员，也适用于开发者和工程师，作为一本标准参考书籍，它持续提供有价值的信息，帮助读者掌握软件测试的精髓，追求卓越的软件质量。"

Contents ◾ xv

16.4.6 LCOM—Lack of Cohesion on Methods .................................................345

16.5 System-Level Complexity .....................................................................................345

Reference ....................................................................................................................... 348

17 Model-Based Testing for Systems of Systems ...........................................................349

17.1 Characteristics of Systems of Systems ...................................................................350

17.2 Sample Systems of Systems ...................................................................................351

17.2.1 e Garage Door Controller (Directed) ..................................................351

17.2.2 Air Traﬃc Management System (Acknowledged) .................................... 352

17.2.3 e GVSU Snow Emergency System (Collaborative)...............................353

17.2.4 e Rock Solid Federal Credit Union (Virtual) .......................................354

17.3 Software Engineering for Systems of Systems .......................................................354

17.3.1 Requirements Elicitation .........................................................................355

17.3.2 Speciﬁcation with a Dialect of UML: SysML ..........................................355

17.3.2.1 Air Traﬃc Management System Classes ..................................355

17.3.2.2 Air Traﬃc Management System Use Cases and Sequence

Diagrams .................................................................................356

17.3.3 Testing ..................................................................................................... 359

17.4 Communication Primitives for Systems of Systems ..............................................359

17.4.1 ESML Prompts as Petri Nets ...................................................................359

17.4.1.1 Petri Net Conﬂict ................................................................... 360

17.4.1.2 Petri Net Interlock .................................................................. 360

17.4.1.3 Enable, Disable, and Activate ..................................................361

17.4.1.4 Trigger ..................................................................................... 361

17.4.1.5 Suspend and Resume ...............................................................361

17.4.2 New Prompts as Swim Lane Petri Nets................................................... 363

17.4.2.1 Request ................................................................................... 363

17.4.2.2 Accept .................................................................................... 363

17.4.2.3 Reject ..................................................................................... 364

17.4.2.4 Postpone ................................................................................. 364

17.4.2.5 Swim Lane Description of the November 1993 Incident ........ 364

17.5 Eﬀect of Systems of Systems Levels on Prompts ....................................................365

17.5.1 Directed and Acknowledged Systems of Systems .................................... 366

17.5.2 Collaborative and Virtual Systems of Systems .........................................367

References .......................................................................................................................367

18 Exploratory Testing ..................................................................................................369

18.1 Exploratory Testing Explored .............................................................................. 369

18.2 Exploring a Familiar Example ..............................................................................371

18.3 Observations and Conclusions ..............................................................................373

References ....................................................................................................................... 374

19 Test-Driven Development ......................................................................................... 375

19.1 Test-en-Code Cycles .........................................................................................375

19.2 Automated Test Execution (Testing Frameworks) ............................................... 384

19.3 Java and JUnit Example ........................................................................................385

19.3.1 Java Source Code .....................................................................................385

19.3.2 JUnit Test Code ...................................................................................... 387

xvi ◾ Contents

19.4 Remaining Questions .......................................................................................... 388

19.4.1 Speciﬁcation or Code Based? .................................................................. 388

19.4.2 Conﬁguration Management? .................................................................. 388

19.4.3 Granularity? ........................................................................................... 388

19.5 Pros, Cons, and Open Questions of TDD ........................................................... 390

19.6 Retrospective on MDD versus TDD ................................................................... 390

20 A Closer Look at All Pairs Testing ...........................................................................395

20.1 e All Pairs Technique ........................................................................................395

20.1.1 Program Inputs ....................................................................................... 396

20.1.2 Independent Variables ............................................................................ 398

20.1.3 Input Order ............................................................................................ 399

20.1.4 Failures Due Only to Pairs of Inputs ...................................................... 403

20.2 A Closer Look at the NIST Study........................................................................ 404

20.3 Appropriate Applications for All Pairs Testing ..................................................... 404

20.4 Recommendations for All Pairs Testing ............................................................... 405

References ...................................................................................................................... 406

21 Evaluating Test Cases .............................................................................................. 407

21.1 Mutation Testing ................................................................................................. 407

21.1.1 Formalizing Program Mutation .............................................................. 408

21.1.2 Mutation Operators ................................................................................ 409

21.1.2.1 isLeap Mutation Testing .......................................................... 410

21.1.2.2 isTriangle Mutation Testing .....................................................411

21.1.2.3 Commission Mutation Testing ................................................412

21.2 Fuzzing ................................................................................................................. 414

21.3 Fishing Creel Counts and Fault Insertion ............................................................. 414

References .......................................................................................................................415

22 Software Technical Reviews .....................................................................................417

22.1 Economics of Software Reviews ...........................................................................417

22.2 Roles in a Review..................................................................................................419

22.2.1 Producer ..................................................................................................419

22.2.2 Review Leader .........................................................................................419

22.2.3 Recorder ................................................................................................. 420

22.2.4 Reviewer ................................................................................................. 420

22.2.5 Role Duplication .................................................................................... 420

22.3 Types of Reviews ................................................................................................. 420

22.3.1 Walkthroughs ..........................................................................................421

22.3.2 Technical Inspections ..............................................................................421

22.3.3 Audits ......................................................................................................421

22.3.4 Comparison of Review Types ................................................................. 422

22.4 Contents of an Inspection Packet ........................................................................ 422

22.4.1 Work Product Requirements .................................................................. 422

22.4.2 Frozen Work Product ............................................................................. 422

22.4.3 Standards and Checklists ........................................................................ 423

22.4.4 Review Issues Spreadsheet ...................................................................... 423

22.4.5 Review Reporting Forms ........................................................................ 424

Contents ◾ xvii

22.4.6 Fault Severity Levels ............................................................................... 425

22.4.7 Review Report Outline ........................................................................... 425

22.5 An Industrial-Strength Inspection Process .......................................................... 426

22.5.1 Commitment Planning ........................................................................... 426

22.5.2 Reviewer Introduction ............................................................................ 427

22.5.3 Preparation ............................................................................................. 427

22.5.4 Review Meeting ...................................................................................... 428

22.5.5 Report Preparation ................................................................................. 428

22.5.6 Disposition ............................................................................................. 428

22.6 Eﬀective Review Culture ..................................................................................... 429

22.6.1 Etiquette ................................................................................................. 429

22.6.2 Management Participation in Review Meetings ..................................... 429

22.6.3 A Tale of Two Reviews ........................................................................... 430

22.6.3.1 A Pointy-Haired Supervisor Review ....................................... 430

22.6.3.2 An Ideal Review ..................................................................... 430

22.7 Inspection Case Study ..........................................................................................431

Reference ....................................................................................................................... 432

23 Epilogue: Software Testing Excellence .....................................................................433

23.1 Craftsmanship ..................................................................................................... 433

23.2 Best Practices of Software Testing ....................................................................... 434

23.3 My Top 10 Best Practices for Software Testing Excellence ...................................435

23.3.1 Model-Driven Agile Development ...........................................................435

23.3.2 Careful Deﬁnition and Identiﬁcation of Levels of Testing .......................435

23.3.3 System-Level Model-Based Testing ......................................................... 436

23.3.4 System Testing Extensions ...................................................................... 436

23.3.5 Incidence Matrices to Guide Regression Testing ..................................... 436

23.3.6 Use of MM-Paths for Integration Testing ............................................... 436

23.3.7 Intelligent Combination of Speciﬁcation-Based and Code-Based

Unit-Level Testing .................................................................................. 436

23.3.8 Code Coverage Metrics Based on the Nature of Individual Units .......... 437

23.3.9 Exploratory Testing during Maintenance ............................................... 437

23.3.10 Test-Driven Development ....................................................................... 437

23.4 Mapping Best Practices to Diverse Projects ......................................................... 437

23.4.1 A Mission-Critical Project ...................................................................... 438

23.4.2 A Time-Critical Project .......................................................................... 438

23.4.3 Corrective Maintenance of Legacy Code ................................................ 438

References ...................................................................................................................... 438

Appendix: Complete Technical Inspection Packet ............................................................439

xix

Preface to the Fourth Edition

Software Testing: A Craftsman’s Approach, Fourth Edition

Software Testing: A Craftsman’s Approach extends an 18-year emphasis on model-based testing with

deeper coverage of path testing and four new chapters. e book has evolved over three editions

and 18 years of classroom and industrial use. It presents a strong combination of theory and prac-

tice, with well chosen, but easily understood, examples. In addition, much of the material from

the ird Edition has been merged, reorganized, and made more concise. Much of the material on

object-oriented software testing has been uniﬁed with procedural software testing into a coherent

whole. In addition, the chapter on path testing contains new material on complex condition test-

ing and Modiﬁed Condition Decision Coverage as mandated by Federal Aviation Authority and

US Department of Defense standards.

Here is a brief summary of the new chapters:

◾ Software reviews, especially technical inspections (Chapter 22). is is really recognized

as “static testing,” whereas the ﬁrst three editions focused on “dynamic testing,” in which

program code executes carefully selected test cases. e material in this chapter is derived

from 20 years of industrial/practical experience in a development organization that had an

extremely mature review process.

◾ An Appendix that contains a full set of documents that are appropriate for an industrial-

strength technical inspection of a set of Use Cases (from UML) that respond to a typical

customer speciﬁcation. e Appendix includes a Use Case Standard, a deﬁnition of Use

Case Fault severities, a technical inspection checklist of potential problems, and typical

reviewer and ﬁnal report forms.

◾ Testing Systems of Systems (Chapter 17). Systems of systems is a relatively new (since 1999)

topic. e practitioner community is just now following the lead of a few university research-

ers, mostly in the area of how to specify a system of systems. is chapter introduces “Swim

Lane Event-Driven Petri Nets,” which have an expressive power very similar to the world-

famous Statecharts. is makes model-based testing possible for systems of systems.

◾ Software complexity (Chapter 16). Most texts only consider cyclomatic (aka McCabe) com-

plexity at the unit level. is chapter extends unit level complexity in two ways and then adds

two views of integration level complexity. ere is a short treatment of the complexities due

to object-oriented programming and also to system level testing. At all levels, complexity is

剩余469页未读，继续阅读

ramissue

粉丝: 354
资源: 1487

第四版《软件测试：匠人之道》：模型驱动的全面指南

Software Testing - A Craftsman's Approach - 2nd Edition

软件测试-Software Testing A Craftsman‘s Approach（中文版）原书第二版

Sams.Software.Testing.2nd.Edition.Jul.2005.part1

Sams.Software.Testing.2nd.Edition.Jul.2005.part2

Sams.Software.Testing.2nd.Edition.Jul.2005.part3

Hard.Problems.in.Software.Testing.Solutions.Using.Testing.as.a.Service.TaaS

.Advanced.Software.Testing.Vol.3.2nd.Edition.193753

Sams.Software.Testing.2nd.Edition.Jul.2005(中文版)

Software.Testing.2nd.Edition （Sams）软件测试（英文版）

Cambridge.Introduction.to.Software.Testing.Jan.2008

最新资源