QA Terms-F

 Software Testing Terminology -F
Fail: A test is deemed to fail if its actual result does not match its expected result.

Failure: Deviation of the component or system from its expected delivery, service or result.

Failure mode: The physical or functional manifestation of a failure. For example, a system in failure mode may be characterized by slow operation, incorrect outputs, or complete termination of execution.

Failure Mode and Effect Analysis (FMEA): A systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to prevent their occurrence. See also Failure Mode, Effect and Criticality Analysis (FMECA).

Failure Mode, Effects, and Criticality Analysis (FMECA): An extension of FMEA, as in addition to the basic FMEA, it includes a criticality analysis, which is used to chart the probability of failure modes against the severity of their consequences. The result highlights failure modes with relatively high probability and severity of consequences, allowing remedial effort to be directed where it will produce the greatest value. See also

Failure Mode and Effect Analysis (FMEA).

Failure rate: The ratio of the number of failures of a given category to a given unit of measure, e.g. failures per unit of time, failures per number of transactions, failures per number of computer runs.

False-fail result: A test result in which a defect is reported although no such defect actually exists in the test object.

False-pass result: A test result which fails to identify the presence of a defect that is actually present in the test object.

false-positive result: See false-fail result. false-negative result: See false-pass result. fault: See defect.

Fault Detection Percentage (FDP): See Defect Detection Percentage (DDP). fault masking: See defect masking.

Fault seeding: The process of intentionally adding known defects to those already in the component or system for the purpose of monitoring the rate of detection and removal, and estimating the number of remaining defects.

Fault seeding tool: A tool for seeding (i.e. intentionally inserting) faults in a component or `system.

Fault tolerance: The capability of the software product to maintain a specified level of performance in cases of software faults (defects) or of infringement of its specified interface. [ISO 9126] See also reliability, robustness.

Fault Tree Analysis (FTA): A technique used to analyze the causes of faults (defects). The technique visually models how logical relationships between failures, human errors, and external events can combine to cause specific faults to disclose.

Feasible path: A path for which a set of input values and preconditions exists which causes it to be executed.

Feature: An attribute of a component or system specified or implied by requirements documentation (for example reliability, usability or design constraints).

Field testing: It is beta testing.

Finite state machine: A computational model consisting of a finite number of states and transitions between those states, possibly with accompanying actions.

Finite state testing: See state transition testing. fishbone diagram: See cause-effect diagram.

Formal review: A review characterized by documented procedures and requirements, e.g. inspection.

Frozen test basis: A test basis document that can only be amended by a formal change control process. See also baseline.

Function Point Analysis (FPA): Method aiming to measure the size of the functionality of an information system. The measurement is independent of the technology. This measurement may be used as a basis for the measurement of productivity, the estimation of the needed resources, and project control.

Functional integration: An integration approach that combines the components or systems for the purpose of getting a basic functionality working early. See also integration testing.

Functional requirement: A requirement that specifies a function that a component or system must perform.

Functional test design technique: Procedure to derive and/or select test cases based on an analysis of the specification of the functionality of a component or system without reference to its internal structure. See also black box test design technique.

Functional testing: Testing based on an analysis of the specification of the functionality of a component or system. See also black box testing.

Functionality: The capability of the software product to provide functions which meet stated and implied needs when the software is used under specified conditions.

Functionality testing: The process of testing to determine the functionality of a software product.



This site uses Akismet to reduce spam. Learn how your comment data is processed.