A scripting technique that uses data files to contain not only test data and expected results, but also keywords related to the application being tested. The …
A statement on the values that underpin Agile software development. The values are: individuals and interactions over processes and tools, working software …
A condition that cannot be decomposed, i.e., a condition that does not contain two or more single conditions joined by a logical operator (AND, OR, XOR).
Procedure to derive and/or select test cases based on an analysis of the specification, either functional or non-functional, of a component or system without …
An input value or output value which is on the edge of an equivalence partition or at the smallest incremental distance on either side of an edge, for example …
A basic block that can be selected for execution based on a program construct in which one of two or more alternative program paths is available, e.g., case, …
The percentage of branches that have been exercised by a test suite. 100% branch coverage implies both 100% decision coverage and 100% statement coverage.
A flaw in a component or system that can cause the component or system to fail to perform its required function, e.g., an incorrect statement or data …
An analysis technique aimed at identifying the root causes of defects. By directing corrective measures at root causes, it is hoped that the likelihood of …
An experience-based test design technique whereby the experienced tester uses a high-level list of items to be noted, checked, or remembered, or a set of rules …
A black-box test design technique in which test cases, described by means of a classification tree, are designed to execute combinations of representatives of …
An analysis method that determines which parts of the software have been executed (covered) by the test suite and which parts have not been executed, e.g., …
The percentage of all single condition outcomes that independently affect a decision outcome that have been exercised by a test case suite. 100% modified …
A form of static analysis based on a representation of unique paths (sequences of events) in the execution through a component or system. Control flow analysis …
An approach to structure-based testing in which test cases are designed to execute specific sequences of events. Various techniques exist for control flow …
The maximum number of linear, independent paths through a program. Cyclomatic complexity may be computed as L = N + 2P, where L = the number of edges/links in …
A scripting technique that stores test input and expected results in a table or spreadsheet, so that a single control script can execute all of the tests in the …
A tool used by programmers to reproduce failures, investigate the state of programs and find the corresponding defect. Debuggers enable programmers to execute …
The percentage of decision outcomes that have been exercised by a test suite. 100% decision coverage implies both 100% branch coverage and 100% statement …
A black-box test design technique in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table.
A procedure to derive and/or select test cases targeted at one or more defect types, with tests being developed from what is known about the specific defect …
The association of a definition of a variable with the subsequent use of that variable. Variable uses include computational (e.g., multiplication) or to direct …
A black-box test design technique in which test cases are designed to execute representatives from equivalence partitions. In principle, test cases are …
A test design technique where the experience of the tester is used to anticipate what defects might be present in the component or system under test as a …
An informal test design technique where the tester actively controls the design of the tests as those tests are performed and uses information gained while …
A technique used to analyze the causes of faults (defects). The technique visually models how logical relationships between failures, human errors, and …
A software testing technique used to discover security vulnerabilities by inputting massive amounts of random data, called fuzz, to the component or system.
A usability review technique that targets usability problems in the user interface or user interface design. With this technique, the reviewers examine the …
A type of peer review that relies on visual examination of documents to detect defects, e.g., violations of development standards and non-conformance to higher …
A statistical technique in decision making that is used for selection of a limited number of factors that produce significant overall effect. In terms of …
A consensus-based estimation technique, mostly used to estimate effort or relative size of user stories in Agile software development. It is a variation of the …
A scripting technique where scripts are structured into scenarios which represent use cases of the software under test. The scripts can be parameterized with …
A programming language/interpreter technique for evaluating compound conditions in which a condition on one side of a logical operator may not be evaluated if …
The disproportionate growth of the number of test cases with growing size of the test basis, when using a certain test design technique. Test case explosion …
A document specifying the test conditions (coverage items) for a test item, the detailed test approach and identifying the associated high-level test cases.
A statement that echoes the Agile manifesto, and defines values for improving the testing process. The values are: flexibility over detailed processes, best …
A usability testing technique where test participants share their thoughts with the moderator and observers by thinking aloud while they solve usability test …
A two-dimensional table, which correlates two entities (e.g., requirements and test cases). The table allows tracing back and forth the links of one entity to …