| 1 | 8 | 9 | |||||||||||||||||||||||
| 2 | |||||||||||||||||||||||||
| 10 | |||||||||||||||||||||||||
| 3 | |||||||||||||||||||||||||
| 4 | |||||||||||||||||||||||||
| 5 | |||||||||||||||||||||||||
| 6 | |||||||||||||||||||||||||
| 7 | |||||||||||||||||||||||||
1. A technique used to select test data by randomly choosing data points from a larger set.
2. A test design technique that focuses on testing all possible combinations of input parameters
3. The extent to which the source code is executed by a test suite
4. A type of testing where test data is selected to validate the expected behavior or correct execution of the software.
5. Data that represents the actual usage scenarios, conditions, and environments in which the software will operate.
6. Test data chosen at the lower and upper limits of input ranges to evaluate system behavior at edge cases
7. Testing done to evaluate the ease of use and user-friendliness of a system
8. Testing performed without any formal test plan or pre-defined steps
9. Ensuring that all relevant and necessary data scenarios are covered during the testing process.
10. A type of testing where test data is intentionally selected to trigger error conditions or invalid inputs.