Op werkdagen voor 23:00 besteld, morgen in huis Gratis verzending vanaf €20

Pragmatic Software Testing: Becoming an Effective and Efficient Test Professional (1e druk 2007)

Paperback Engels 2007 9780470127902
Verwachte levertijd ongeveer 8 werkdagen


Testing even a simple system can quickly turn into a potentially infinite task. Faced with tight costs and schedules, testers need to have a toolkit of practical techniques combined with hands-on experience and the right strategies in order to complete a successful project. World-renowned testing expert Rex Black provides you with the proven methods and concepts that test professionals must know. He presents you with the fundamental techniques for testing and clearly shows you how to select and apply successful strategies to test a system with budget and time constraints.

Black begins by discussing the goals and tactics of effective and efficient testing. Next, he lays the foundation of his technique for risk-based testing, explaining how to analyze, prioritize, and document risks to the quality of the system using both informal and formal techniques. He then clearly describes how to design, develop, and, ultimately, document various kinds of tests. Because this is a hands-on activity, Black includes realistic, life-sized exercises that illustrate all of the major test techniques with detailed solutions.

By the end of this book, you'll know more about the nuts and bolts of testing than most testers learn in an entire career, and you'll be ready to put those ideas into action on your next test project.

With the help of real-world examples integrated throughout the chapters, you'll discover how to:
- Analyze the risks to system quality
- Allocate your testing effort appropriately based on the level of risk
- Choose the right testing strategies every time
- Design tests based on a system's expected behavior (black box) or internal structure (white box)
- Plan and perform integration testing
- Explore and attack the system
- Focus your hard work to serve the needs of the project

The author's companion Web site provides exercises, tips, and techniques that can be used to gain valuable experience and effectively test software and systems.


Aantal pagina's:366
Hoofdrubriek:IT-management / ICT


Wees de eerste die een lezersrecensie schrijft!

Geef uw waardering

Zeer goed Goed Voldoende Matig Slecht

Over Rex Black

With a quarter-century of software and systems engineering experience, Rex Black is President of RBCS (www.rbcs-us.com), a leader in software, hardware, and systems testing. For over a dozen years, RBCS has delivered services in consulting, outsourcing, and training for software and hardware testing. Employing the industry's most experienced and recognized consultants, RBCS conducts product testing; builds and improves testing groups; and hires testing staff for hundreds of clients worldwide. Ranging from Fortune 20 companies to start-ups, RBCS's clients save time and money through improved product development, decreased tech support calls, improved corporate reputation, and more. As the leader of RBCS, Rex is the most prolific author practicing in the field of software testing today. His popular first book, Managing the Testing Process, has sold over 30,000 copies around the world, including Japanese, Chinese, and Indian releases. His three other books on testing, Critical Testing Processes, Foundations of Software Testing, and Pragmatic Software Testing, have also sold tens of thousands of copies, including Hebrew, Indian, Chinese, Japanese and Russian editions. He has written over twenty-five articles, presented hundreds of papers, workshops, and seminars, and given about thirty keynote speeches at conferences and events around the world. Rex is the President of both the International Software Testing Qualifications Board (ISTQB) and the American Software Testing Qualifications Board (ASTQB).

Andere boeken door Rex Black



Part 1: Goals, Strategies, and Tactics.
1. What Does It Mean to Be Pragmatic?
-What Do Effective and Efficient Mean?
-What Effects Do You Want?
-What Is the Right Level of Efficiency?
-Avoiding Redundancy.
-Reducing Cost.
-What Software Testing Isn't…But Is Often Thought to Be.
-Five Phases of a Tester's Mental Life.
-Other Founding Views on Testing.
-Testing as a Form of Quality Risk Management.
-So What Is the Test Team All About?
-What Does “Quality” Mean to You?

2. Triangle Test Exercise.
-Exercise: The Triangle Test.
-Your Solution for the Triangle Test.
-Your Solution for the Triangle Test (Continued).
-Author's Triangle Test Solution.

3. Aligning Testing with the Project.
-Why Do Organizations Test?
-Perspectives on Testing.
-Testing in Context.
-Common Test Phases and Objectives.
-Testing Throughout the Organization.
-The V Model.
-Evolutionary and Incremental Models.
-The Spiral Model.
-Regrettably Common Model: Code and Fix.
-Testing Maintenance Releases.
-System Integration.
-Hardware/Software Development.
-The Test Process.

4. Understanding Test Strategies, Tactics, and Design.
-Aligning Mission, Strategies, and Tactics.
-Analytical Test Strategies.
-Model-Based Test Strategies.
-Methodical Test Strategies.
-Process-Oriented Test Strategies.
-Dynamic Test Strategies.
-Philosophical Test Strategies.
-Regression Strategy 1: Repeat All Tests.
-Regression Strategy 2: Repeat Some Tests.
-Three Other Regression Strategies.
-Tactics: Categories of Testing Techniques.
-Strategic and Tactical Considerations.
-The Test System.
-Classic Principles for Test Design.
-Phases of Test Development.
-Synopsis of Test Strategies, Tactics, and Design.

Part 2: Risk-Based Testing.
5. Understanding Risks to System Quality.
-Categories of Quality Risks.
-Performance and Reliability.
-Stress, Capacity, and Volume.
-Installation and Deinstallation.
-Maintenance and Maintainability.
-Usability and User Interface.
-Data Quality.
-Error and Disaster Handling and Recovery.
-Date and Time Handling.
-Configuration and Compatibility.
-Networked, Internetworked, and Distributed.
-Standards and Regulatory Compliance.
-Timing and Coordination.
-Can You Think of Other Quality Risks?

6. Aligning Testing with Quality Risks.
-Prioritize Risks to System Quality.
-Testing, Customer Usage, and System Configurations.
-Approaches for Quality Risks Analysis.
-Informal Quality Risk Analysis.
-Tips for Risk Analysis.
-Challenges of Risk Analysis.

7. Quality Risk Analysis Exercise.
-My Solution.
-Comments on My Solution.
-A Funny Thing Happened to Me on the Way to the Quality Risks… .
-Bonus Exercise.
-My Solution.
-Comments on My Solution.
-Bonus Example: Grays and Blues Quality Risk Analysis.

Part 3: Static Testing.
8. Reviews and Other Static Tests.
-Testing Requirements and Designs.
-Reviews Costs and Benefits.
-Types of Reviews.
-Reviews for Verification and Validation.
-Reviews as a Way to Improve the Process, Improve the System, and Reduce Costs.
-Answers to the Three Questions about Static Testing.
-Reviews as a Way to Achieve Consensus and Understanding.
-The Review Process, Roles, and Responsibilities.
-Deliverables and Ground Rules from Reviews.
-Common Requirements and Design Bugs.
-Reviewing (and Testing) Documentation.
-Other Static Tests.

9. Review Exercise.
-Your Solution.
-My Solution.
-Comments on My Solution.
-Bonus Exercise: Reviewing Triangle Requirements Title Page.
-Triangle Requirements Review Using Wiegers's List.
-The Requirements Bugs You Found.
-My Solution: Requirements Bugs.
-Comments on My Solution.

Part 4: Behavioral Testing.
10. Equivalence Classes and Boundary Values.
-Equivalence Partitioning.
-Boundary Value Analysis.
-Real Numbers.
-Character and String.
-Beyond Functional Classes and Boundaries.

11. Equivalence Classes and Boundary Values Exercise.
-Functional Boundaries and Classes.
-My Solution and Comments.
-Nonfunctional Boundaries and Classes.
-Omninet Marketing Requirements Document (v0.3).
-Omninet System Requirements Document (v0.2).

12. Use Cases, Live Data, and Decision Tables.
-Use Cases and Scenario Tests.
-Nouns and Verbs, Adjectives and Adverbs.
-Live Data and Customer Tests.
-Decision Tables.

13. Decision Table Exercise.
-Decision Table Tests.
-My Solution and Comments.
-Decision Tables and Boundary Values.
-My Solution and Comments.
-Building a Decision Table for Testing.
-My Solution and Comments.

14. State Transition Diagrams.
-Describing Systems with States Using State Transition Diagrams.
-State Tables.
-Printer Server State Transition Diagram.

15. State Transition Diagram Exercise.
-Kiosk States.
-My Solution and Comments.
-ATM State Models.
-My Solution and Comments.
-Grays and Blues and State Transition Diagrams.
-My Solution and Comments.

16. Domain Testing.
-Combinatorial Explosions.
-A Domain Example Using Frequent-Flyer Programs.
-Possible Domain Test Values.
-An Aerospace Example.
-When Domain Rules Change.
-Domain Analysis Summary.
-Complex Domain Testing Example.
-A General Rule for Complex Domains.

17. Domain Testing Exercise.
-My Solution and Comments.

18. Orthogonal Arrays and All Pairs.
-Combinatorial Explosions.
-Orthogonal Arrays and All-Pairs Tables.
-Two Orthogonal Arrays.
-Selecting an Orthogonal Array.
-Applying Orthogonal Arrays to a Complicated Real-World Example.
-All-Pairs Tables.
-Other Thoughts on Configuration Testing.

19. Orthogonal Arrays Exercise.
-My Solution and Comments.

20. Reactive Testing.
-General Facts about Reactive Tests.
-Error Guessing, Attacks, and Bug Taxonomies.
-Bug Hunting.
-Exploratory Tests.
-Other Sources of Inspiration for Reactive Testing.
-Advantages and Disadvantages.
-A Case Study of Exploratory Testing.
-Part V Structural Testing.

21. Control-Flow Testing.
-Code Coverage.
-McCabe Cyclomatic Complexity.

22. Control-Flow Testing Exercise.
-My Solution and Comments.

23. Data-Flow Testing.

24. Data-Flow Testing Exercise.
-My Solutions and Comments.

25. Integration Testing.
-Drivers and Stubs.
-Integration Techniques.
-Backbone Integration.
-McCabe Basis Paths for Integration.
-Enhanced Hex Converter Program.
-Call Flow.

26. Integration Basis Test Exercise.
-My Solution and Comments.

Part 5 : Appendices.
Appendix A: Omninet: The Internet Everywhere Marketing Requirements Document.
1. Scope.
1.1 Terms, Acronyms, and Abbreviations.
1.2 Applicable Documents.
2. Required release date.
3. Description of requirements.
3.1 General technical requirements.
3.1.1 Welcome.
3.1.2 Payment.
3.1.3 Internet Browser.
3.1.4 Performance.
3.1.5 Localization.
3.1.6 Content Control.
3.1.7 Session Termination.
3.1.8 Confidentiality.
3.2 Administration.
3.2.1 Software Updates.
3.2.2 View Kiosks.
3.2.3 View Users.
3.2.4 Modify User.
3.2.5 Terminate User.

Appendix B: Omninet: The Internet Everywhere System Requirements Document.
-Functionality System Requirements.
-Reliability System Requirements.
-Usability System Requirements.
-Efficiency System Requirements.
-Maintainability System Requirements.
-Portability System Requirements.
-Design Models.
-Omninet System Architecture.
-Payment Processing Decision Table.
-Kiosk Module Flow.
-Kiosk State-Transition Diagram.
-Kiosk State-Transition Table.
-Kiosk OS/Browser/Connection Speed Configuration Orthogonal Array.

Appendix C: Bibliography and Other Recommended Readings.

RBCS Company Profile.

Alle 100 bestsellers


Populaire producten



        Pragmatic Software Testing: Becoming an Effective and Efficient Test Professional (1e druk 2007)