| Ad-Hoc Testing |
Testing performed without any formal test plan or pre-defined steps |
| Boundary Values |
Test data chosen at the lower and upper limits of input ranges to evaluate system behavior at edge cases |
| Code Coverage |
The extent to which the source code is executed by a test suite |
| Data Completeness |
Ensuring that all relevant and necessary data scenarios are covered during the testing process. |
| Negative Testing |
A type of testing where test data is intentionally selected to trigger error conditions or invalid inputs. |
| Pairwise Testing |
A test design technique that focuses on testing all possible combinations of input parameters |
| Positive Testing |
A type of testing where test data is selected to validate the expected behavior or correct execution of the software. |
| Random Sampling |
A technique used to select test data by randomly choosing data points from a larger set. |
| Real-World Data |
Data that represents the actual usage scenarios, conditions, and environments in which the software will operate. |
| Test Coverage |
The measurement of the extent to which testing has covered a system |
| Test Data |
Data used in testing to execute test cases and evaluate the behavior of a system |
| Usability Testing |
Testing done to evaluate the ease of use and user-friendliness of a system |
