| |
Glossary |
|
| |
............................................................................................................................... |
|
| |
Functional Testing: See also Black Box Testing .
- Testing the features and operational behavior of a product to ensure they correspond to its specifications.
- Testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions.
|
|
| |
Glass Box Testing: A synonym for White Box Testing . |
|
| |
|
|
| |
High Order Tests: Black-box tests conducted once the software has been integrated. |
|
| |
|
|
| |
Inspection: 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). |
|
| |
|
|
| |
Integration Testing: 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. |
|
| |
|
|
| |
|
|
| |
Installation Testing: 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. |
|
| |
|
|
| |
Load Testing: See Performance Testing. |
|
| |
|
|
| |
Loop Testing: A white box testing technique that exercises program loops. |
|
| |
|
|
| |
Metric: A standard of measurement. Software metrics are the statistics describing the structure or content of a program. A metric should be a real objective measurement of something such as number of bugs per lines of code. |
|
| |
|
|
| |
Monkey Testing: Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out. |
|
| |
|
|
| |
Negative Testing: Testing aimed at showing software does not work. Also known as "test to fail". See also Positive Testing. |
|
| |
|
|
| |
Path Testing: Testing in which all paths in the program source code are tested at least once. |
|
| |
|
|
| |
Performance 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". |
|
| |
|
|
| |
Positive Testing: Testing aimed at showing software works. Also known as "test to pass". See also Negative Testing. |
|
| |
|
|
| |
Quality Assurance: 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. |
|
| |
|
|
| |
Quality Audit: 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. |
|
| |
|
|
| |
Quality Control: The operational techniques and the activities used to fulfill and verify requirements of quality. |
|
| |
|
|
| |
Quality Policy: The overall intentions and direction of an organization as regards quality as formally expressed by top management. |
|
| |
|
|
| |
Quality System: The organizational structure, responsibilities, procedures, processes, and resources for implementing quality management. |
|
| |
|
|
| |
Ramp Testing: Continuously raising an input signal until the system breaks down. |
|
| |
|
|
| |
Recovery Testing: Confirms that the program 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. |
|
| |
|
|
| |
Regression Testing: Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made. |
|
| |
|
|
| |
Sanity Testing: Brief test of major functional elements of a piece of software to determine if its basically operational. See also Smoke Testing . |
|
| |
|
|
| |
Scalability Testing: Performance testing focused on ensuring the application under test gracefully handles increases in work load. |
|
| |
|
|
| |
Security Testing: Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can access the functions available to their security level. |
|
| |
|
|
| |
Smoke Testing: A quick-and-dirty test that the major functions of a piece of software work. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire. |
|
| |
|
|
| |
Soak Testing: Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed. |
|
| |
|
|
| |
Software Requirements Specification: A deliverable that describes all data, functional and behavioral requirements, all constraints, and all validation requirements for software/ |
|
| |
|
|
| |
Software Testing: A set of activities conducted with the intent of finding errors in software. |
|
| |
|
|
| |
Static Analysis: Analysis of a program carried out without executing the program. |
|
| |
|
|
| |
Static Testing: Analysis of a program carried out without executing the program. |
|
| |
|
|
| |
Storage Testing: Testing that verifies the program under test stores data files in the correct directories and that it reserves sufficient space to prevent unexpected termination resulting from lack of space. This is external storage as opposed to internal storage. |
|
| |
|
|
| |
Previous ... |
|
| |
|
|
