Glossary of Terms beginning Alphabet-D
Data Definition:
Data Definition is an executable statement where a variable is assigned a value.
Data Dictionary:
Data Dictionary is a database that contains definitions of all data items defined during analysis.
Data Driven Testing:
Data Driven Testing is a testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet. It is a common technique in Automated Testing.
Data Flow:
Data Flow is an abstract representation of the sequence and possible changes of the state of data objects, where the state of an object is any of: creation, usage, or destruction.
Data Flow Analysis:
Data Flow Analysis is a form of static analysis based on the definition and usage of variables.
Data Flow Coverage:
Data Flow Coverage refers to the percentage of definition-use pairs that have been exercised by a test case suite. It is a variation of path coverage, which considers only the sub-paths from variable assignments to subsequent references of the variables. The advantage of this metric is that the paths reported have direct relevance to the way the program handles the data. One disadvantage of this metric is that it does not include decision coverage. Another disadvantage is its complexity.
Data Flow Diagram:
Data Flow Diagram is a modeling notation that represents a functional decomposition of a system.
Data Flow Test:
Data flow test is a white box test design technique in which test cases are designed to execute definition and use pairs of variables.
Data Pool:
Datapool is a test dataset, a collection of related data records which supplies data values to the variables in a test script during test script playback. Datapools are used to supply realist data and to stress an application with a realistic amount of data. When we create a data-driven test by using Functional Test, we select the objects in an application-under-test to data-drive. Functional Test creates a datapool in which we can edit and add data. we can use a single test script repeatedly with varying input and response data.
Debugging:
Broadly debugging is the process of Fixing the identified Bugs. It involves a process of analyzing and rectifying the syntax errors, logic errors and all other types of errors identified during the process of testing. It must be clearly differentiated from “Testing” which refers to locating or identifying the errors or bugs. Debugging occurs as a consequence of successful testing. It is an exercise to connect the external manifestation of the error and the internal cause of the error.
Debugging Tool:
Debugging Tool is a tool used by programmers to reproduce failures, investigate the state of programs and find the corresponding defect. Debuggers enable programmers to execute programs step by step, to halt a program at any program statement and to set and examine program variables.
Decision:
Decision is a program point at which the control flow has two or more alternative routes. A node with two or more links to separate branches.
Decision Coverage:
Decision Coverage is a white-box testing technique which measures the number or percentage of the decision directions executed by the designed test case. For example 100% Decision coverage indicates that all decision directions had been executed at least once during the testing.
Decision Condition Testing:
Decision Condition Testing is a white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes.
Decision Coverage:
Decision Coverage refers to the percentage of decision outcomes that have been exercised by a test suite. 100% decision coverage implies both 100% branch coverage and 100% statement coverage.
Decision Table:
Decision Table is a tool to do documentation of unique combinations of conditions and associated results in order to derive unique test cases for validation testing. It is a table showing combinations of inputs and their associated outputs and actions (effects), which can be used to design test cases.
Decision Table Testing:
Decision Table Testing is a black box test design techniques in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table.
Decision Testing:
Decision Testing is a white box test design technique in which test cases are designed to execute decision outcomes.
Decision Outcome:
Decision Outcome is the result of a decision (which therefore determines the branches to be taken).
Defect:
Defect refers to nonconformance to requirements or functional / program specification. It is a flaw in a component or system, which can cause the component, or system to fail to perform its required function, e.g. an incorrect statement or data definition. A defect, if encountered during execution, may cause a failure of the component or system
Defect Density:
Defect Density is a software metric defined as: Total number of defects per LOC (lines of code). Alternatively It can be: Total number of defects per Size of the Project. Here the measure of “Size of the Project” can be number of Function Points, Number of Feature Points, number of Use Cases or KLOC (Kilo Lines of Code) etc
Defect Detection Percentage or DDP:
Defect Detection Percentage is the number of defects found by a test phase, divided by the number found by that test phase and any other means afterwards.
Defect Report:
Defect Report is a document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function.
Defect Management:
Defect Management is the process of recognizing, investigating, taking action and disposing of defects. It involves recording defects, classifying them and identifying the impact.
Defect Masking:
Defect Masking refers to an occurrence in which one defect prevents the detection of another.
Defect Tracking Tools:
Defect Tracking Tools are the tools to do documentation of defects as detected during the testing and for keeping a track of their status till they are fully resolved.
Definition-Use Pair:
Definition-Use Pair refers to the association of the definition of a variable with the use of that variable. Variable uses include computational (e.g. multiplication) or to direct the execution of a path (“predicate” use).
Dependency Testing:
Dependency Testing examines an application’s requirements for pre-existing software, initial states and configuration in order to maintain proper functionality.
Depth Testing:
Depth Testing is a test that exercises a feature of a product in full detail.
Deliverable:
Deliverable is any (work) product that must be delivered to someone other that the (work) product�s author.
Design-Based Testing:
Design Based Testing is an approach to testing in which test cases are designed based on the architecture Design-based testing and/or detailed design of a component or system (e.g. tests of interfaces between components or systems).
Desk Check:
Desk Check is a verification technique conducted by the author of the artifact to verify the completeness of their own work. This is a standalone technique which does not involve anyone else.
Development Testing:
Development Testing is a formal or informal testing conducted during the implementation of a component or system, usually in the development environment by developers.
Direct URL Testing:
Direct URL Testing is a type of testing in which the test engineer specifies the direct URL�s of some secured page and checks as to whether the page gets accessed or not.
Documentation Testing:
Documentation Testing refers to the testing the quality of the documentation, e.g. user guide or installation guide.
Domain:
Domain is the set from which valid input and/or output values can be selected.
Driver:
Driver is a software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system.
Dynamic Analysis:
Dynamic Analysis is the process of evaluating behavior, e.g. memory performance, CPU usage, of a system or component during execution.
Dynamic Comparison:
Dynamic Comparison refers to the comparison of actual and expected results, performed while the software is being executed, for example by a test execution tool.
Dynamic Testing:
Dynamic Testing is used to describe the testing of the dynamic behavior of the software code. It involves actual compilation & running of the software by giving input values and checking if the output is as expected. It is the validation portion of Verification and Validation.
Explanation to All Alphabets in the Glossary of Terms
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.