A Practical Guide to Testing Object-Oriented Software / John D. McGregor, David A. Sykes.
Material type: TextSeries: Addison-Wesley object technology seriesPublication details: Boston, Ma. : Addison-Wesley, 2001.Description: xiv, 393 p. : ill. ; 24 cmISBN:- 0201325640
- QA76.T48 M47 2001
Item type | Current library | Call number | Copy number | Status | Barcode | |
---|---|---|---|---|---|---|
Books | Library First Floor | QA76.T48 M47 2001 (Browse shelf(Opens below)) | 1 | Available | 1061 |
Browsing Library shelves, Shelving location: First Floor Close shelf browser (Hides shelf browser)
No cover image available | No cover image available | No cover image available | ||||||
QA76 .S365 2004 Sams teach yourself UML in 24 hours / | QA76 .S533 1997 Introductory Computer Science With C++ Volume 1/ | QA76 .T353 2007 Mobile Computing: Technology,Applications,and Service Creation/ | QA76.T48 M47 2001 A Practical Guide to Testing Object-Oriented Software / | QA76 .T85 2010 Windows 7 resource kit / | QA76 .U62 2003 المهارات الحاسوبية الأساسية والبرمجيات الجاهزة / | QA76 .U62 2003 المهارات الحاسوبية الأساسية والبرمجيات الجاهزة / |
Includes bibliographical references (p. 375-379) and index.
1. Introduction. Who Should Read This Book? What Software Testing Is and Isnt. What Is Different about Testing OO Software? Overview of Our Testing Approach. Test Early. Test Often. Test Enough. The Testing Perspective. Organization of This Book. Conventions Used in This Book. A Continuing Example - Brickles. Basic Brickles Components. Brickles Physics. Game Environment. 2. The Testing Perspective. Testing Perspective. Object-Oriented Concepts. Object. Message. Interface. Class. Inheritance. Polymorphism. Development Products. Analysis Models. Design Models. Source Code. Summary. 3. Planning for Testing. A Development Process Overview. A Testing Process Overview. Risk Analysis - A Tool for Testing. Risks. Risk Analysis. A Testing Process. Planning Issues. Dimensions of Software Testing. Who Performs Testing? Which Pieces Are Tested? When is Testing Performed? How Is Testing Performed? How Much Testing Is Adequate? Roles in the Testing Process. A Detailed Set of Test Activities. Planning Activities. Scheduling Testing Activities. Estimation. A Process for Testing Brickles. Document Templates. Test Metrics. Summary. 4. Testing Analysis and Design Models. An Overview. Place in the Development Process. The Basics of Guided Inspection. Evaluation Criteria. Organization of the Guided Inspection Activity. Basic Roles. Individual Inspection. Preparing for the Inspection. Specifying the Inspection. Realistic Models. Selecting Test Cases for the Inspection. Creating Test Cases . Completing Checklists. The Interactive Inspection Session. Testing Specific Types of Models. Requirements Model. Analysis Models. Design Models. Testing Again. Testing Models for Additional Qualities. Summary. Model Testing Checklist. Appendix. A Process Definition for Guided Inspection. Steps in the Process. Detailed Step Descriptions. Roles in the Process. 5. Class Testing Basics. Class Testing. Ways to Test a Class. Dimensions of Class Testing. Constructing Test Cases. Adequ.
You will find information on such important topics as: * Testing analysis and design models, including selecting test cases to guide design inspections * Testing components, frameworks, and product lines * The testing challenges of inheritance and polymorphism * How to devise an effective testing strategy * Testing classes, including constructing a test driver and test suites * Testing object interactions, covering sampling test cases, off-the-shelf components, protocol testing, and test patterns * Testing class hierarchies, featuring subclass test requirements * Testing distributed objects, including threads, life cycle testing, and Web server testing * Testing systems, with information on stress, life cycle, and performance testing One comprehensive example runs throughout the book to demonstrate testing techniques for each stage of development. In addition, the book highlights important questions that testers should ask when faced with specific testing tasks. The authors acknowledge that testing is often viewed as a necessary evil, and that resources allocated to testing are often limited.
There are no comments on this title.