Data flow analysis

It is a process for collecting run-time information about data in programs without actually executing them.

Hazard Analysis

A technique used to characterize the elements of risk. The result of a hazard analysis will drive the methods used for development and testing of a system.

Control flow analysis

A form of static analysis based on a representation of sequences of events (paths) in the execution through a component or system.

Control flow analysis

A form of static analysis based on a representation of sequences of events (paths) in the execution through a component or system.

Dynamic analysis

The process of evaluating behavior, e.g. memory performance, CPU usage, of a system or component during execution.

Test Point Analysis (TPA)

A formula based test estimation method based on function point analysis.

Status accounting

An element of configuration management, consisting of the recording and reporting of information needed to manage a configuration effectively. This information includes a listing of the approved configuration identification, the status of proposed changes to the configuration, and the implementation status of the approved changes.

Function Point Analysis (FPA)

A 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.

Mutation testing

Mutation testing (sometimes also called mutation analysis) is a method of software testing, which involves modifying program's source code in small ways. These, so-called mutations, are based on well-defined mutation operators that either mimic typical user mistakes (such as using the wrong operator or variable name) or force the creation of valuable tests (such as driving each expression to zero).

Monkey test

A monkey test is a unit test that runs with no specific test in mind. The monkey in this case is the producer of any input. For example, a monkey test can enter random strings into text boxes to ensure handling of all possible user input or provide garbage files to check for loading routines that have blind faith in their data

Stub

A routine that doesn't actually do anything other than declare itself and the parameters it accepts. Stubs are used commonly as placeholders for routines that still need to be developed. The stub contains just enough code to allow it to be compiled and linked with the rest of the program.

Heuristic evaluation

A static usability test technique to determine the compliance of a user interface with recognized usability principles (the so-called “heuristics”).

Testware

Artifacts produced during the test process required to plan, design, and execute tests, such as documentation, scripts, inputs, expected results, set-up and clear-up procedures, files, databases, environment, and any additional software or utilities used in testing.

Orthogonal array

A 2-dimensional array constructed with special mathematical properties, such that choosing any two columns in the array provides every pair combination of each number in the array.

Thread Testing

A version of component integration testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by levels of a hierarchy

Wide Band Delphi

An expert based test estimation technique that aims at making an accurate estimation using the collective wisdom of the team members

Security testing

The process to determine that an IS (Information System) protects data and maintains functionality as intended. The six basic security concepts that need to be covered by security testing are: confidentiality, integrity, authentication, authorisation, availability and non-repudiation.

Fault Tree Analysis

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.

Status Accounting

An element of configuration management, consisting of the recording and reporting of information needed to manage a configuration effectively. This information includes a listing of the approved configuration identification, the status of proposed changes to the configuration, and the implementation status of the approved changes.