Structured Testing - McCabe and Associates

More documents

Recommendations

Info

20 Figure 3-5. Control flow graph with complexity 6. Figure 3-6. Control flow graph with complexity 8.
Figure 3-7. Control flow graph with complexity 12. Figure 3-8. Control flow graph with complexity 17. 21
Page 1 and 2: NIST Special Publication 500-235 St
Page 3: Abstract The purpose of this docume
Page 7 and 8: CONTENTS Abstract..................
Page 9 and 10: 11 Maintenance ....................
Page 11 and 12: 1 Introduction 1.1 Software testing
Page 13 and 14: used to represent software systems
Page 15 and 16: Figure 1-1 shows the dependencies a
Page 17 and 18: 2 Cyclomatic Complexity Cyclomatic
Page 19 and 20: Figure 2-2. Control flow graph for
Page 21 and 22: Virtual Edge Figure 2-4. Control fl
Page 23 and 24: 2.4 Example of v(G) and basis paths
Page 25 and 26: than the cyclomatic complexity numb
Page 27 and 28: 3 Examples of Cyclomatic Complexity
Page 29: Figure 3-3. Control flow graph with
Page 33 and 34: 4 Simplified Complexity Calculation
Page 35 and 36: In addition to counting predicates
Page 37 and 38: Figure 4-6 shows a C code module wi
Page 39 and 40: 4.3 Use of automated tools The most
Page 41 and 42: 5 Structured Testing Structured tes
Page 43 and 44: Next, with structured testing, test
Page 45 and 46: Figure 5-2. Code for module “coun
Page 47 and 48: that satisfies the structured testi
Page 49: 5.7 Critical software Different typ
Page 52 and 53: First, for every decision in the mo
Page 54 and 55: 6.4 Example of the baseline method
Page 56 and 57: Of the tests in Figure 6-2, the bas
Page 58 and 59: integration testing can be combined
Page 60 and 61: tured testing at the module level r
Page 62 and 63: ule 3 illustrates that a conditiona
Page 64 and 65: 7.5 Integration complexity The inte
Page 66 and 67: Although a basis set of paths throu
Page 68 and 69: Figure 7-7 illustrates the structur
Page 70 and 71: When abstraction works well, it hid
Page 72 and 73: are objects of a class type, the ex
Page 74 and 75: ment is to provide evidence that th
Page 77 and 78: 9 Complexity Reduction Although the
Page 79 and 80: Figure 9-3. Code after removing unn
Page 81 and 82:
There are many situations in which
Page 83 and 84:
show the reengineered functions “
Page 85 and 86:
Figure 9-10.Graph for structured mo
Page 87:
In addition to the trade-off betwee
Page 90 and 91:
understood code, since the connecti
Page 92 and 93:
tured logic is superimposed on the
Page 94 and 95:
complexity may not be obvious from
Page 96 and 97:
11.4 Reuse of testing information A
Page 98 and 99:
call resolutions based on complexit
Page 100 and 101:
[DAHL] Dahl, O. and E. Dijkstra and
Page 102 and 103:
[MCCABE5] McCabe, T. and A. Watson,
Page 104 and 105:
[WARD] Ward, W., “Software Defect
Page 106 and 107:
A.3 Walsh 96 The propensity to make
Page 108 and 109:
to avoid changing very complex proc
Page 110 and 111:
testing and maintenance. The projec
Page 112 and 113:
The suggested explanation is that o
Page 114 and 115:
A.21 Koshgoftaar et al Koshgoftaar,
Page 116 and 117:
B.1.2 The module Figure B-1 shows t
Page 118 and 119:
dealer’s hand value. Those two va
Page 120 and 121:
The ninth functional test is a win
Page 122 and 123:
B.2 Experimental comparison of stru
Page 124:
114
show all

Structured Testing - McCabe and Associates

Create successful ePaper yourself

Delete template?

Save as template?