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