Muutke küpsiste eelistusi

Testing Object-Oriented Software: Life Cycle Solutions 1999 ed. [Kõva köide]

  • Formaat: Hardback, 209 pages, kõrgus x laius: 235x155 mm, kaal: 1110 g, XIX, 209 p., 1 Hardback
  • Ilmumisaeg: 17-Dec-1999
  • Kirjastus: Springer-Verlag New York Inc.
  • ISBN-10: 0387988963
  • ISBN-13: 9780387988962
Teised raamatud teemal:
  • Kõva köide
  • Hind: 48,70 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Tavahind: 57,29 €
  • Säästad 15%
  • Raamatu kohalejõudmiseks kirjastusest kulub orienteeruvalt 2-4 nädalat
  • Kogus:
  • Lisa ostukorvi
  • Tasuta tarne
  • Tellimisaeg 2-4 nädalat
  • Lisa soovinimekirja
  • Formaat: Hardback, 209 pages, kõrgus x laius: 235x155 mm, kaal: 1110 g, XIX, 209 p., 1 Hardback
  • Ilmumisaeg: 17-Dec-1999
  • Kirjastus: Springer-Verlag New York Inc.
  • ISBN-10: 0387988963
  • ISBN-13: 9780387988962
Teised raamatud teemal:
The rise of object-oriented (00) software development seems to have helped improve software quality, but it has not, of course, eliminated all possibility of error. Thus, software testing is at least as important today as it ever has been. Testing, as a centerpiece of quality assurance efforts, only increases in value as society becomes more and more reliant on software. Testing 00 components and even 00 systems is not very difficult once you know how to do it. But until now there have been few accounts of how to do it well and none that adequately characterize testing across the life cycle of large 00 software production efforts. This book combines insights from research on 00 testing with insights from industrial testing efforts to produce an account that should be valuable to anyone interested in the theory and practice of testing 00 software. This book provides extensive coverage of testing methods applicable to 00 software development, as well as discussions of underlying concepts and technical underpinnings that enable you to devise additional techniques of your own. It is unlikely that you will apply every test, process, review criterion, or metric described in this book to your software project. If you have a small project, it is unlikely that you will apply more than a few of them. But the breadth of coverage allows you to select and customize them with full knowledge of the alternatives and of the options available if you need to extend testing efforts.

Muu info

Springer Book Archives
Foreword vii
Preface ix
List of Figures
xviii
Introduction
1(4)
Why a Book on Testing Object-Oriented Software?
2(1)
Outline of Book
3(2)
Software Process and Testing Models
5(15)
Software Process Models
7(6)
Capability Maturity Model (CMM)
8(2)
Personal Software Process (PSP)
10(3)
Object-Oriented Software Development and Testing Model
13(5)
Object-Oriented Software Development Model
13(1)
Parallel Testing Model
14(3)
Testing Ripples
17(1)
Summary
18(2)
Impact of Object Orientation on Testing
20(7)
Encapsulation
21(1)
Information Hiding
22(1)
Abstraction
23(1)
Inheritance
24(1)
Reuse
24(1)
Testability of Object-Oriented Systems
25(1)
Summary
26(1)
Requirements Testing
27(9)
Objective
28(1)
Approach
29(1)
Activities
30(3)
Typical Activities in Requirements Testing
31(2)
Resources
33(1)
Effort
34(1)
Acceptance Criteria
34(1)
Summary
34(2)
Design Testing
36(13)
Objective
37(1)
Approach
38(2)
Design Walk-Throughs
39(1)
Prototyping
40(1)
Activities
40(5)
Typical Activities in Design Testing
41(4)
Resources
45(1)
Effort
46(1)
Acceptance Criteria
47(1)
Summary
47(2)
Base Classes Unit Testing
49(23)
Objective
49(2)
Approach
51(3)
Activities
54(15)
Assumptions
54(1)
Typical Activities in Unit Testing
55(13)
Analysis
68(1)
Resources
69(1)
Effort
70(1)
Acceptance Criteria
70(1)
Summary
71(1)
Derived Classes Unit Testing
72(17)
Test Procedure
73(14)
Draw Derived Enchanced Call Graph (ECGderived)
73(1)
Draw MaDUMderived
73(3)
Fill MaDUMderived
76(6)
Test Local Attributes
82(2)
Retest Inherited Attributes
84(3)
Analysis
87(1)
Summary
88(1)
Testing C++ Special Features
89(8)
Static Data Members
89(2)
Function Pointers
91(1)
Structs as Data Members
91(1)
Nested Classes
92(1)
Member Access Controlaccess control
93(1)
Composite Classes
94(1)
Abstract Classes
95(1)
Summary
96(1)
Code Reviews
97(17)
Objective
97(2)
Approach
99(1)
Activities
100(4)
Typical Activities in Code Reviews
100(4)
Resources
104(1)
Effort
105(1)
Acceptance Criteria
105(1)
Language-Independent Errors Checklist
106(4)
Data Reference Errors
106(1)
Data Declaration Errors
107(1)
Computation Errors
107(1)
Comparison Errors
108(1)
Control Flow Errors
108(1)
Input/Output Errors
108(1)
Interface Errors
109(1)
Domain Errors
109(1)
Performance Errors
110(1)
Other Errors
110(1)
Object-Oriented Errors Checklist
110(3)
Summary
113(1)
Integration Testing
114(14)
Objective
114(2)
Approach
116(1)
Activities
117(8)
Structural Integration Testing
117(5)
Functional Integration Testing
122(3)
Resources
125(1)
Effort
126(1)
Acceptance Criteria
126(1)
Summary
127(1)
Integrated-System Testing
128(17)
Objective
129(1)
Approach
130(1)
Activities
131(9)
Sanity Testing
131(1)
Functional Testing
132(2)
Human Factors Testing
134(2)
Performance Testing
136(2)
Capacity Testing
138(1)
Documentation Testing
139(1)
Resources
140(2)
Effort
142(1)
Acceptance Criteria
142(1)
Summary
143(2)
A SampleStatistic Class Source Code 145(6)
A.1 Header File
145(2)
A.2 Source File
147(4)
B SampleHistogram Class Source Code 151(5)
B.1 Header File
151(2)
B.2 Source File
153(3)
C PriorityQueue Class Source Code 156(8)
C.1 Eiffel Implementation
156(3)
C.2 C++ Header File
159(1)
C.3 C++ Source File
160(4)
D Algorithms for Drawing MaDUM 164(7)
D.1 Base Class MaDUM Algorithm
164(3)
D.2 Derived Class MaDUM Algorithm
167(4)
E Test Data Adequacy Axioms 171(8)
E.1 ``Obvious'' Axioms
171(1)
E.1.1 Applicabilityapplicability
172(1)
E.1.2 NonExhaustive Applicability
172(1)
E.1.3 Monotonicity
172(1)
E.1.4 Inadequate Empty Set
172(1)
E.1.5 Renaming
172(1)
E.1.6 Complexity
172(1)
E.1.7 Statement Coverage
172(1)
E.2 ``Not-so-obvious'' Axioms
172(7)
E.2.1 Antiextensionality
172(3)
E.2.2 General Multiple Change
175(1)
E.2.3 Antidecomposition
176(1)
E.2.4 Anticomposition
177(2)
References 179(22)
Index 201