The art of software testing. Myers (2nd edition) (2004) (The art of software testing. Myers (2nd edition) (2004).pdf), страница 38

A set of procedures and error-detection techniquesfor group code readings that is often used as part of the testing cycleto detect errors. Usually a group of people act as a “computer” toprocess a small set of test cases.white-box testing. A type of testing in which you examine the internal structure of a program.INDEXAAcceptance testing, 128, 144with Extreme Programming,179, 185Application programming interface (API), 177Application server, 196Architecture testing, 204Automated debugging tools,158, 160Automated testingAutomated test tools, 120BBacktrack debugging, 168Basic e-commerce architecture,194Beck, Kent, 188Big-bang testing, 105Black-box testing, 9–11, 44,205.

See also Equivalencepartitioningmethodologies of, 52vs. white-box testing, 114BONUS module, 94, 101boundary value analysis of,102Boolean logic network, 85Bottom-up testing, 116–119disadvantages, 117vs. top-down testing, 109Boundary conditions, 59Boundary-value analysis, 44, 59,196compared to equivalence classtesting, 59input boundaries for, 102program example, 60, 61weakness of, 65Branch coverage, 45Branch decision testing, exceptions to successful testing, 46Branching statement, Java codesample, 47, 48Browser compatibility testing,198, 204Brute force debugging, 158problems with, 160Business layer, 196, 201business layer testing, 199,205–208Business tier, 196CC++ compiler testing, 10Case stories, 179227228IndexCause-effect graph:converting to decision table,81definition, 66symbols, 68used to derive test cases, 71Cause-effect graphing, 44,65–88, 149described, 85for program specificationanalysis, 86Check4Prime.java, 186, 213Check4PrimeTest.java, 186, 216Checklists, 27–38comparison errors, 31computation errors, 30control flow errors, 32data-declaration errors, 29data reference errors, 27input/output errors, 35inspection error, 36interface errors, 34Client-server applications, 193Client-server architecture,194–196, 201Code inspection, 22, 24–26benefits, 26checklist for, 27process, 26time required, 26Code walkthrough, 38Comparison errors, 31Compatibility/configuration/conversion testing, 138Compiler testing, 10Computation errors, 30Condition coverage, 44, 46, 97Configuration testing, 138Content testing, 204Continuous testing, 179Control-flow errors, 32Control-flow graph, 11DData access layer, 196, 201data access layer testing, 199,208–212Data checking, 23Data-declaration errors, 29Data-driven testing, 9Data integrity, 210Data reference errors, 27Data-sensitivity errors, 13Data tier, 196Data validation, 207Debugging, 157–175by backtracking, 168–169brute force method, 158–160by changing the program, 159cost of, 23by deduction, 164–168error analysis and, 173by induction, 160–164principles of, 170–173procedures for, 147by testing, 169Decision/condition-coveragetesting, 49, 99and/or masking, 49Decision coverage, 44, 45Decision coverage testing, definition, 47IndexDecision table, 79from cause-effect graph, 81Deductive debugging, 164test cases, 166Desk checking, 40Development vs.

testing, 127Documentation testing, 142Driver module, 106EE-commerce architecture,194–196Economics of program testing, 9End-user test, 144Equivalence classes:compared to boundary-valueanalysis, 59identifying, 53, 54program example, 56splitting, 55Equivalence partitioning, 44,52steps to complete, 53weakness of, 65Eratosthenes, sieve of, 190Erroneous input checks, 55Error analysis debugging, 173Error guessing, 44, 88example, 89Error-locating debuggingprinciples, 170Error-repairing debuggingprinciples, 171Errors:checklists for, 27–35comparison, 31229computation, 30control-flow, 32data-declaration, 29data reference, 27input/output, 35interface, 34Errors found/errors remainingrelationship, 20Exhaustive input testing, 9, 10,13Exhaustive path testing, 11, 13External specification, 124, 125Extreme Programming (XP),177acceptance testing with,178–183, 185basics of, 178case stories with, 179continuous testing with, 179Extreme Testing with, 183practices, 179–181project example, 182refactoring with, 180strengths and weaknesses,182unit testing with, 179,183–185Extreme Testing (XT), 177, 178,183–190applied, 186concepts of, 183program sample, 213test case design, 186test driver for, 189test harness with, 190Extreme unit testing, 183230IndexFFacility testing, 133Fault tolerance and recoverability, 211Flow-control graph, 12FORTRAN DISPLAY command:objectives for, 132test cases for, 133Function test, purpose of, 128,130Function testing, 129–130completion criteria for, 149,151GGamma, Erich, 188Graphical user interface (GUI), 1Guidelines for program testing,15HHigher-order testing, 123–155defined, 123Human factors, 135Human testing, 21procedures of, 142See also Code inspection,Desk checking, Peerratings, WalkthroughIIdentifying test cases, 55Incremental testing: 105–109compared to nonincrementaltesting, 107See also Bottom-up testing,Top-down testingIndependent test agency, 155Induction debugging, 160example, 163steps to follow, 161Inductive assertions, 140Input checks, erroneous, 55Input/output-driven testing, 9Input/output errors, 35Inspection error checklist, 36Inspections, 21checklist for, 27–40and walkthroughs, 22Inspection team, 24duties, 25members, 25Installability testing, 139Installation testing, 128, 144test cases for, 145Integration testing, 105Interface errors, 34Internet applications:architecture testing with, 204Business layer testing, 205–208challenges, 197client-server architecture,194–196content testing with, 204data integrity with, 210Data layer testing with, 208data validation of, 207fault tolerance with, 211performance goals for, 198performance testing of, 206Presentation layer testing, 202recoverability with, 211response time testing with,209Indexstress testing with, 207testing strategies for, 200transactional testing of, 208Internet application testing,193–212challenges with, 196Isosceles triangle, 2JJava code sample, branchingstatement, 47, 48Java program sample, 186, 213,216JUnit, 188LLogic coverage testing, 44.

Seealso White-box testingLogic-driven testing, 11Loop testing, 33MMean time between failures(MTBF), 140, 200maximizing, 211Mean time to recovery(MTTR), 141, 142, 200Memory dump, 159Missing path errors, 13Module testing, 91–121, 151with automated tools, 120completion criteria for, 148performing the test, 120purpose of, 128,test case design, 92MTBF. See Mean time betweenfailures (MTBF)231MTEST, 61, 63error guessing with, 89output boundaries for, 64test cases for, 63MTTR. See Mean time torecoveryMulticondition coverage criterion, 101Multiple-condition coverage,44Multiple condition testing,49–50NNetwork connectivity, 200Non-computer-based testing,21Nonincremental testing, 105,106OOff-by-one errors, 33PPath testing, 45Peer ratings, 40Performance testing, 137, 206PL/1, 92, 101Presentation layer, 196, 201presentation layer testing, 199,202–205Presentation tier, 196Preventing software errors,125Prime numbers:calculation, 190list, 221232Print statement debugging,159Procedure testing, 142Program:control-flow graph, 11, 12debugging, 16inspections, 21reviews, 21walkthroughs, 21Program errors:checklist for inspections, 27comparison, 31computation, 30control-flow, 32data-declaration, 29data-sensitivity, 13determining number of, 149input/output, 35interface, 34missing path, 13probability, 19Program testing:as destructive process, 8assumption, 6black-box, 9definition, 5, 6economics of, 9example, 56guidelines, 14, 15human factor considerations,135principles of, 14strategies, 9success, 7white-box, 11who should test, 16IndexRRandom-input testing, 43Rapid application development,177RDBMS.

See Relational database management system(RDBMS)Recovery testing, 141Refactoring, 180Regression testing, 18, 147Relational database, 196Relational database managementsystem (RDBMS), 196Reliability testing, 139Response-time testing, 209SScalene triangle, 2Security testing, 137Serviceability testing, 142Sieve of Eratosthenes, 190Software development, vs.

testing, 127Software development cycle,123, 124Software documentation, 125Software errors:causes, 124, 125preventing, 125Software objectives, externalspecification, 124Software prediction, 140Software proving, 140Software reliability engineering(SRE), 140Software requirements, 125IndexSoftware testing:vs. development, 127human factor consideration,135principles of, 14–20summarized, 15Software test plan, 146SRE. See Software reliabilityengineering (SRE)Statement coverage, 44Storage dump debugging, 158Storage testing, 138Stress testing, 134, 207Stub module, 106, 110System testing, 130–144, 151fifteen categories of, 133–142performing, 143purpose of, 128stress testing, 134, 207TTest-based debugging, 169Test case design, 43–90.