1、.aacceptance testing:testing conducted to enable a user/customer to determine whetherto accept a software product. normally performed to validate the software meets a set ofagreed acceptance criteria.accessibility testing:verifying a product is accessible to the people having disabilities(deaf, blin

2、d, mentally disabled etc.).ad hoc testing:a testing phase where the tester tries to break the system by randomlytrying the systems functionality. can include negative testing as well. see alsomonkeytesting .agile testing:testing practiceforprojectsusing agilemethodologies,treatingdevelopmentasthecus

3、tomeroftesting and emphasizingatest-first designparadigm.see also test driven development .application binary interface (abi):a specification defining requirements for portability ofapplications in binary forms across defferent system platforms and environments.applicationprogramminginterface(api):

4、aformalizedset ofsoftwarecalls androutines that can be referenced by an application program in order to access supportingsystem or network services.automatedsoftwarequality(asq): the useof softwaretools,such asautomatedtesting tools, to improve software quality.automated testing:? testing employing

5、software tools which execute tests without manual intervention. can be applied in gui, performance, api, etc. testing.? the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other testcontrol and test

6、 reporting functions.bbackus-naur form:a metalanguage used to formally describe the syntax of a language.basic block:a sequence of one or more consecutive, executable statements containingno branches.basis path testing:a white box test case design technique that uses the algorithmic flowof the progr

7、am to design tests.basis set:the set of tests derived usingbasis path testing .baseline: the point at which some deliverable produced during the software engineeringprocess is put under formal change control.beta testing: testing of a rerelease of a software product conducted by customers.binary por

8、tability testing:testing an executable application for portability across systemplatforms and environments, usually for conformation to anabi specification.black boxtesting: testing basedonananalysisof the specificationof apieceofsoftware withoutreferenceto itsinternalworkings.the goal is to testhow

9、ponent conforms to the published requirements for the component.bottomuptesting: anapproachtointegrationtesting wherethelowest levelcomponents are tested first, then used to facilitate the testing of higher level components.the process is repeated until the component at the top of the hie

10、rarchy is tested.boundary testing:test which focus on the boundary or limit conditions of the softwarebeing tested. (some of these tests are stress tests).bug: a faultinaprogramwhichcausestheprogramtoperform inanunintendedorunanticipated manner.boundaryvalueanalysis:bvaissimilar toequivalencepartiti

11、oningbut focusesoncorner cases or values that are usually out of range as defined by the specification. hismeans that if a function expects all values in range of negative 100 to positive 1000, testinputs would include negative 101 and positive 1001.branch testing:testing in which all branches in th

12、e program source code are tested atleast once.breadth testing:a test suite that exercises the full functionality of a product but does nottest features in detail.ccast: computer aided software testing.capture/replay tool:a test tool that records test input as it is sent to the software undertest. th

13、e input cases stored can then be used to reproduce the test at a later time. mostcommonly applied to gui test tools.cmm: the capabilitymaturity model for software (cmm or sw-cmm)is amodelforjudging the maturity of the software processes of an organization and for identifying thekey practices that ar

14、e required to increase the maturity of these processes.causeeffectgraph: a graphicalrepresentationofinputsandtheassociatedoutputseffects which can be used to design test cases.codecomplete:phaseof development wherefunctionalityisimplementedinentirety;bug fixes are all that are left. all functions fo

15、und in the functional specifications have beenimplemented.code coverage:ananalysis method that determineswhichparts of thesoftware havebeen executed (covered) by the test case suite and which parts have not been executedand therefore may require additional attention.code inspection:a formal testing

16、technique where the programmer reviews source codewith a group who askquestionsanalyzing theprogram logic,analyzingthecodewithrespectto achecklistof historically commonprogrammingerrors,and analyzingitscompliance with coding standards.code walkthrough:a formal testing technique where source code is

17、traced by a groupwith a small set of test cases, while the state of program variables is manually monitored,to analyze the programmers logic and assumptions.coding: the generation of source code.compatibility testing:testing whether software is compatible with other elements of asystem with which it

18、 should operate, e.g. browsers, operating systems, or hardware.component:a minimal software item for which a separate specification is available.component testing:see unit testing .concurrencytesting:multi-user testing gearedtowardsdeterminingtheeffectsofaccessing thesameapplicationcode,module or da

19、tabaserecords.identifiesandmeasures the level of locking, deadlocking and use of single-threaded code and lockingsemaphores.conformancetesting:theprocessoftestingthatanimplementationconformstothespecificationonwhichit isbased.usuallyappliedtotestingconformancetoaformalstandard.context driven testing

20、:the context-driven school of software testing is flavor ofagiletesting that advocates continuous and creative evaluation of testing opportunities in lightof the potential information revealed and the value of that information to the organizationright now.conversiontesting:testing of programsorproce

21、duresusedtoconvertdata fromexisting systems for use in replacement systems.cyclomaticcomplexity:ameasureofthelogicalcomplexityofanalgorithm,used inwhite-box testing.ddata dictionary:a databasethatcontainsdefinitionsof all dataitemsdefinedduringanalysis.data flow diagram:a modeling notation that repr

22、esents a functional decomposition of asystem.data driven testing: testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet. a common techniquein automated testing .debugging: the process of finding and removing the causes of s

23、oftware failures.defect: nonconformance to requirements or functional / program specificationdependency testing:examines an applications requirements for pre-existing software,initial states and configuration in order to maintain proper functionality.depth testing:a test that exercises a feature of

24、a product in full detail.dynamic testing:testing software through executing it. see alsostatic testing .eemulator:adevice,computerprogram,or systemthatacceptsthesameinputsandproduces the same outputs as a given system.endurancetesting: checksfor memoryleaksorotherproblems that mayoccurwithprolonged

25、execution.end-to-end testing:testing a complete application environment in a situation that mimicsreal-worlduse, such asinteractingwith a database, usingnetwork communications, orinteracting with other hardware, applications, or systems if appropriate.equivalenceclass: a portionof a componentsinput

26、oroutputdomainsforwhichthecomponents behaviour is assumed to be the same from the components specification.equivalencepartitioning:a testcasedesigntechniquefor a componentinwhichtestcases are designed to execute representatives from equivalence classes.exhaustivetesting:testingwhichcoversallcombinat

27、ionsofinputvaluesandpreconditions for an element of the software under test.ffunctionaldecomposition:a techniqueusedduringplanning,analysisanddesign;creates a functional hierarchy for the software.functional specification:a document that describes in detail the characteristics of theproduct with reg

28、ard to its intended features.functional testing:see alsoblack box testing.? testing the features and operational behavior of a product to ensure they correspond to its specifications.? testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in

29、 response to selected inputs and execution conditions.gglass box testing:a synonym forwhite box testing .gorilla testing:testing one particular module,functionality heavily.grayboxtesting:a combinationof black box andwhite boxtesting methodologies:testingapieceofsoftware against its specificationbut

30、 usingsome knowledge of itsinternal workings.hhigh order tests:black-box tests conducted once the software has been integrated.iindependenttestgroup (itg): a groupof peoplewhose primaryresponsibilityissoftware testing,inspection: a group review quality improvement process for written material. it co

31、nsists oftwo aspects; product (document itself) improvement andprocess improvement (of bothdocument production and inspection).integrationtesting:testingof combinedparts of anapplicationtodetermine iftheyfunction together correctly. usually performed after unit and functional testing. this type ofte

32、sting is especially relevant to client/server and distributed systems.installation testing:confirms that the application under test recovers from expected orunexpectedevents without lossof data or functionality. events caninclude shortage ofdisk space, unexpected loss of communication, or power out

33、conditions.jk.lload testing:see performance testing.localizationtesting:thistermrefersto makingsoftwarespecificallydesignedforaspecific locality.loop testing:a white box testing technique that exercises program loops.mmetric: a standardof measurement.softwaremetricsare the statisticsdescribingthestr

34、ucture or content of a program. a metric should be a real objective measurement of something such as number of bugs per lines of code.monkey testing: testing a system or an application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out.nnegative t

35、esting:testing aimed at showing software does not work. also known as testto fail. see alsopositive testing.oppath testing:testing in which all paths in the program source code are tested at leastonce.performancetesting: testingconductedto evaluatethe complianceof a systemorcomponentwith specifiedpe

36、rformancerequirements.often this is performedusinganautomated test tool to simulate large number of users. also know as load testing.positive testing:testing aimed at showing software works. also known as test to pass.see alsonegative testing.qquality assurance: all those planned or systematic actio

37、ns necessary to provide adequate confidence that a product or service is of the type and quality needed and expected by the customer.quality audit: a systematic and independent examination to determine whether quality activities and related results comply with planned arrangements and whether these

38、arrangements are implemented effectively and are suitable to achieve objectives.quality circle:a group of individuals with related interests that meet at regular intervals to.consider problems or other matters related to the quality of outputs of a process and to thecorrection of problems or to the

39、improvement of quality.qualitycontrol:theoperational techniques and the activitiesusedto fulfilland verifyrequirements of quality.quality management:that aspect of the overall management functionthat determinesand implements the quality policy.quality policy:the overall intentions and direction of a

40、n organization as regards qualityas formally expressed by top management.qualitysystem: theorganizational structure, responsibilities,procedures,processes,and resources for implementing quality management.rrace condition: a cause of concurrency problems. multiple accesses to a shared resource, at le

41、ast one of which is a write, with no mechanism used by either to moderate simultaneous access.ramp testing:continuously raising an input signal until the system breaks down.recoverytesting: confirmsthat the programrecoversfromexpectedor unexpectedevents without loss of data or functionality. events

42、can include shortage of disk space, unexpected loss of communication, or power out conditions.regression testing: retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.release candidate:a pre-release v

43、ersion, which contains the desired functionality of thefinal version,but whichneedsto be testedfor bugs(whichideallyshouldbe removedbefore the final version is released).s sanitytesting:brieftestofmajorfunctionalelementsof a pieceof softwaretodetermine if its basically operational. see alsosmoke tes

44、ting .scalability testing:performance testing focused on ensuring the application under testgracefully handles increases in work load.securitytesting: testingwhichconfirmsthattheprogramcanrestrictaccesstoauthorized personnel and that the authorized personnel can access the functions available to the

45、ir security level.smoke testing: a quick-and-dirty test that the major functions of a piece of software work. originated in the hardware testing practice of turning on a new piece of hardware for.the first time and considering it a success if it does not catch on fire.soak testing: running a system

46、at high load for a prolonged period of time. for example, running several times more transactions in an entire day (or night) than wouldbe expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed.software requirements specificat

47、ion:a deliverable that describes all data, functionaland behavioral requirements, all constraints, and all validation requirements for software/softwaretesting:a setofactivitiesconductedwith the intent offindingerrorsinsoftware.static analysis:analysis of a program carried out without executing the

48、program.static analyzer:a tool that carries out static analysis.static testing:analysis of a program carried out without executing the program.storagetesting:testing that verifies the programunderteststoresdata filesinthecorrect directories and that it reserves sufficient space to prevent unexpected

49、 terminationresulting from lack of space. this is external storage as opposed to internal storage.stress testing: testing conducted to evaluate a system or component at or beyond thelimits ofitsspecifiedrequirements to determine theloadunderwhichit failsandhow.often this isperformance testingusing a

50、 very high level of simulated load.structural testing:testing based on an analysis of internal workings and structure of apiece of software. see alsowhite box testing .system testing:testing that attempts to discover defects that are properties of the entiresystem rather than of its individual components.testa