|
Glossary of Software QA/Testing
Part:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
Desk Checking
A form of manual static analysis usually performed by the originator. Source code documentation, etc., is visually checked against requirements and standards.
Dynamic Analysis
The process of evaluating a program based on execution of that program. Dynamic analysis approaches rely on executing a piece of software with selected test data.
Usability?
"Usability" means ease of use; the ease with which a user can learn to operate, prepare inputs for, and interpret the outputs of a software product.
Evaluation
The process of examining a system or system component to determine the extent to which specified properties are present.
Execution
The process of a computer carrying out an instruction or instructions of a computer.
Exhaustive Testing: Executing the program with all possible combinations of values for program variables.
Failure
The inability of a system or system component to perform a required function within specified limits. A failure may be produced when a fault is encountered.
Failure-directed Testing
Testing based on the knowledge of the types of errors made in the past that are likely for the system under test.
Fault
A manifestation of an error in software. A fault, if encountered, may cause a failure.
Fault Tree Analysis
A form of safety analysis that assesses hardware safety to provide failure statistics and sensitivity analyses that indicate the possible effect of critical failures.
Fault-based Testing
1. Testing that employs a test data selection strategy designed to generate test data capable of demonstrating the absence of a set of pre-specified faults, typically, frequently occurring faults.
2. This type of testing allows for designing test cases based on the client specification or the code or both. It tries to identify plausible faults (areas of design or code that may lead to errors). For each of these faults a test case is developed to "flush" the errors out. These tests also force each line of code to be executed
Part:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
| 