| 1 | 10 | ||||||||||||||||||||||||
| 2 | 13 | ||||||||||||||||||||||||
| 3 | |||||||||||||||||||||||||
| 4 | |||||||||||||||||||||||||
| 14 | |||||||||||||||||||||||||
| 8 | 9 | 11 | 12 | ||||||||||||||||||||||
| 5 | |||||||||||||||||||||||||
| 6 | |||||||||||||||||||||||||
| 7 | |||||||||||||||||||||||||
1. A type of software testing where the tester goes through the entire software application, step by step, to ensure that there are no defects or issues.
2. An error that occurs during arithmetic operations, such as division by zero or overflow/underflow.
3. A table used to track the values of variables, expressions, and statements as a program is executed.
4. An error that occurs when a file that is being accessed is not found.
5. An error that occurs during the execution of a program, leading to abnormal termination or unexpected behavior.
6. A testing technique that focuses on the functionality and behavior of a software system without examining its internal code structure.
7. A testing technique that examines the internal code structure of a software system to identify any defects or vulnerabilities.
8. A type of data validation that ensures a value is provided and not left blank or empty.
9. A process of verifying that an item is unique within a certain context.
10. A sequence of test steps that represent a particular usage or workflow of a software application or system.
11. The practice of retesting previously tested software to ensure that changes or fixes have not introduced new defects or regression bugs.
12. A type of data validation that verifies if a value falls on the lower or upper boundary of an acceptable range.
13. The accuracy and consistency of data throughout its lifecycle.
14. An expression that can either be true or false.