| 1 | 14 | |||||||||||||||||||||
| 2 | ||||||||||||||||||||||
| 18 | ||||||||||||||||||||||
| 15 | 3 | 16 | ||||||||||||||||||||
| 4 | ||||||||||||||||||||||
| 17 | ||||||||||||||||||||||
| 5 | ||||||||||||||||||||||
| 6 | ||||||||||||||||||||||
| 7 | 19 | |||||||||||||||||||||
| 8 | ||||||||||||||||||||||
| 9 | ||||||||||||||||||||||
| 10 | ||||||||||||||||||||||
| 11/12 | ||||||||||||||||||||||
| 13 |
1. A series of steps performed to confirm the correctness and validity of data.
2. A detailed document that outlines the approach, objectives, and scope of testing for a particular software product.
3. A sequence of test steps that represent a particular usage or workflow of a software application or system.
4. An error that occurs when an operation or function is applied to an object of inappropriate type.
5. A type of data validation that examines the structure and format of data to ensure it adheres to predefined rules.
6. The process of ensuring that data is accurate, consistent, and complies with predefined rules.
7. The process of manually examining source code to identify bugs, improve code quality, and share knowledge among team members.
8. The degree to which a software application or system has been tested, usually measured in terms of code coverage or functionality coverage.
9. An error that occurs when attempting to access an element outside the bounds of an array or collection.
10. A storage location in a computer program that can hold different values at different times.
11. An error in a program due to improper use of programming language syntax.
12. An error in the syntax of a programming language that prevents the code from being parsed and executed.
13. A type of testing that identifies vulnerabilities and weaknesses in a system's security measures and ensures its protection against unauthorized access.
14. The process of checking the accuracy and integrity of entered data.
15. An error that occurs when a program tries to access a null object or null reference.
16. The process of executing a program one line or instruction at a time, allowing for detailed inspection and analysis of its behavior.
17. A type of testing performed by a select group of users to evaluate the software and provide feedback before its official release.
18. A testing technique that divides the input values into equivalent partitions and selects test data from each partition.
19. The data used to execute test cases and verify the behavior and correctness of a software application or system.