| 1 | 17 | ||||||||||||||||||||||||
| 2 | |||||||||||||||||||||||||
| 15 | |||||||||||||||||||||||||
| 3 | 18 | ||||||||||||||||||||||||
| 4 | |||||||||||||||||||||||||
| 5 | |||||||||||||||||||||||||
| 6 | |||||||||||||||||||||||||
| 7 | |||||||||||||||||||||||||
| 8 | |||||||||||||||||||||||||
| 16 | 9 | ||||||||||||||||||||||||
| 10 | |||||||||||||||||||||||||
| 11 | |||||||||||||||||||||||||
| 12 | |||||||||||||||||||||||||
| 13 | |||||||||||||||||||||||||
| 14 | |||||||||||||||||||||||||
1. The degree to which a software application or system has been tested, usually measured in terms of code coverage or functionality coverage.
2. An error that occurs when a mathematical operation produces a result that is too large to be represented within the available memory or data type.
3. A device that captures and reads barcodes to retrieve encoded information.
4. A type of data validation that confirms if a value meets a specified length requirement.
5. Ensuring that data is accurate, complete, and fits the required format or rules.
6. The process of ensuring that data is accurate, consistent, and complies with predefined rules.
7. A snapshot of a program's memory state at a particular point in time, allowing for inspection of variables and data structures.
8. An error that occurs during arithmetic operations, such as division by zero or overflow/underflow.
9. A type of software testing performed to identify and eliminate all possible issues before releasing the software to the end-users.
10. An error that occurs when trying to access an index that is out of range for a sequence.
11. A testing technique where specific code segments or modules are replaced with placeholder code to simulate the behavior of dependent components.
12. A testing technique that examines the internal code structure of a software system to identify any defects or vulnerabilities.
13. The process of checking the accuracy and integrity of entered data.
14. An error in the syntax of a programming language that prevents the code from being parsed and executed.
15. Ensuring that data follows a defined structure or schema.
16. A type of software testing performed by end-users before the final release of the software to ensure its reliability and usability.
17. A series of steps performed to confirm the correctness and validity of data.
18. The accuracy and consistency of data throughout its lifecycle.