QA Testing

This term refers to making software specifically designed for a specific locality.

Testing one particular module, functionality heavily.

A combination of Black Box and White Box testing methodologies? testing a piece of software against its specification but using some knowledge of its internal workings.

Black-box tests conducted once the software has been integrated.

A group of people whose primary responsibility is software testing,

A group review quality improvement process for written material. It consists of two aspects; product (document itself) improvement and process improvement (of both document production and inspection).

Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.

Confirms that the application under test recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.

The organizational structure, responsibilities, procedures, processes, and resources for implementing quality management.

The overall intentions and direction of an organization as regards quality as formally expressed by top management.

That aspect of the overall management function that determines and implements the quality policy.

The operational techniques and the activities used to fulfill and verify requirements of quality.

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 the correction of problems or to the improvement of quality.

A systematic and independent examination to determine whether quality activities and related results comply with planned arrangements and whether these arrangements are implemented effectively and are suitable to achieve objectives.

All those planned or systematic actions necessary to provide adequate confidence that a product or service is of the type and quality needed and expected by the customer.

Testing aimed at showing software works. Also known as "test to pass". See also Negative Testing.

Testing conducted to evaluate the compliance of a system or component with specified performance requirements. Often this is performed using an automated test tool to simulate large number of users. Also know as "Load Testing".

Testing in which all paths in the program source code are tested at least once.

Testing aimed at showing software does not work. Also known as "test to fail". See also Positive Testing.

Analysis of a program carried out without executing the program. A tool that carries out static analysis.