| 1 | 11 | ||||||||||||||||||||
| 2 | |||||||||||||||||||||
| 9 | 10 | ||||||||||||||||||||
| 3 | |||||||||||||||||||||
| 4 | |||||||||||||||||||||
| 12 | |||||||||||||||||||||
| 5 | |||||||||||||||||||||
| 6 | |||||||||||||||||||||
| 7 | |||||||||||||||||||||
| 8 | |||||||||||||||||||||
1. A type of software testing performed by end-users before the final release of the software to ensure its reliability and usability.
2. A test where the program is run with sample data to verify the correctness of its logic.
3. A type of software testing performed to identify and eliminate all possible issues before releasing the software to the end-users.
4. A testing technique where specific code segments or modules are replaced with placeholder code to simulate the behavior of dependent components.
5. The practice of testing individual software components, such as functions or methods, to ensure their correctness.
6. The process of combining software modules or components and testing them as a group to verify their interactions and functionality.
7. The final phase of software testing where a system is evaluated for its acceptance by the end users or stakeholders.
8. The practice of retesting previously tested software to ensure that changes or fixes have not introduced new defects or regression bugs.
9. 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.
10. A testing technique that examines the internal code structure of a software system to identify any defects or vulnerabilities.
11. The process of testing an integrated software system to evaluate its compliance with the specified system requirements.
12. A testing technique that focuses on the functionality and behavior of a software system without examining its internal code structure.