Term
|
Definition
| Smallest testable part of an application; could be a program, function, procedure or module |
|
|
Term
|
Definition
| Testing of individual software components or modules |
|
|
Term
|
Definition
| Type of unit testing that determines whether the program does what it is supposed to do or not |
|
|
Term
|
Definition
| Individual software modules are combined and tested as a group, occurs after unit testing and before system testing |
|
|
Term
|
Definition
| Is also known as validation testing and provides a consistent, repeatable validation of each change to an application under development or being modified. It is selective retesting of an application or system that has been modified to insure that no previously working components, functions, or features fail as a result of the repairs. Ensures that changes or corrections have not introduced new errors |
|
|
Term
|
Definition
| All of the system elements are tested as a whole |
|
|
Term
|
Definition
| Is conducted when the system is just ready for implementation, used to ensure that the system satisfies the quality standards and the users |
|
|
Term
|
Definition
| Ensures that the functional aspects expected by the users is well addressed by the new system, 2 types- alpha and beta testing |
|
|
Term
|
Definition
| First stage user acceptance testing, performed by users within the organization |
|
|
Term
|
Definition
| Second stage user acceptance testing, generally performed by users external to the organization for real world exposure |
|
|
Term
| Backup and recovery testing |
|
Definition
| Tests the ability of an application to be restarted after failure |
|
|
Term
|
Definition
| Verifies that the instruction guides are helpful and accurate |
|
|
Term
|
Definition
| Testing to determine the extent to which the software product is understood, easy to learn, easy to operate and attractive to the users under specified conditions |
|
|
Term
|
Definition
| Type of integration testing that insures that the application works with differently configured systems based on what the users have or may have. Example web interface testing requires testing for compatibility with different browsers and connection speeds |
|
|
Term
|
Definition
| Is used to evaluate and understand the application’s scalability when, for example, more users are added or the volume of data increases. |
|
|
Term
|
Definition
| Is a performance testing at higher than normal simulated loads to determine the load under which it fails and how it fails |
|
|
Term
|
Definition
| Is a performance test that is the opposite of stress tests and tests the capability of the application to function properly under expected normal production conditions and measure the response times for critical transactions or processes to determine if they are within limits specified in the business requirements |
|
|
Term
| Production verification testing |
|
Definition
| Is a final opportunity to determine if the software is ready for release. Its purpose is to simulate the production cutover as closely as possible and for a period of time simulate real business activity. As a sort of full dress rehearsal, it should identify anomalies or unexpected changes to existing processes introduced by the new application. |
|
|
