| 1 | 14 | ||||||||||||||||||||||||
| 10 | 2 | 17 | |||||||||||||||||||||||
| 3 | |||||||||||||||||||||||||
| 12 | 16 | ||||||||||||||||||||||||
| 11 | 4/13 | 18 | |||||||||||||||||||||||
| 5 | |||||||||||||||||||||||||
| 6 | |||||||||||||||||||||||||
| 7 | 15 | ||||||||||||||||||||||||
| 8 | |||||||||||||||||||||||||
| 9 | |||||||||||||||||||||||||
1. A process of verifying that an item is unique within a certain context.
2. Ensuring that data is accurate, complete, and fits the required format or rules.
3. The degree to which a software application or system has been tested, usually measured in terms of code coverage or functionality coverage.
4. An error that occurs when a file that is being accessed is not found.
5. The data used to execute test cases and verify the behavior and correctness of a software application or system.
6. An error that occurs during the execution of a program, leading to abnormal termination or unexpected behavior.
7. A combination of values, variables, and operators that can be evaluated to produce a result.
8. An error in the logic or algorithm of a program that causes incorrect results or unexpected behavior.
9. A device that captures and reads barcodes to retrieve encoded information.
10. The practice of retesting previously tested software to ensure that changes or fixes have not introduced new defects or regression bugs.
11. A named section of code that performs a specific task and can be called by other sections of code.
12. A specific set of inputs, conditions, and expected results used to determine whether a software system is functioning correctly.
13. A type of data validation that verifies if the value is in the correct format or follows a specific pattern.
14. The process of manually examining source code to identify bugs, improve code quality, and share knowledge among team members.
15. A type of data validation where the value is checked to make sure it falls within a specified range.
16. The practice of inserting messages or information into the program's output during execution for debugging or monitoring purposes.
17. 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.
18. A symbol or word used to compare two values and produce a boolean result.