| 1/7 | ||||||||||||||||||||||
| 2 | ||||||||||||||||||||||
| 9 | 10 | |||||||||||||||||||||
| 3 | ||||||||||||||||||||||
| 4 | ||||||||||||||||||||||
| 5/8 | ||||||||||||||||||||||
| 6 |
1. The degree to which a software application or system has been tested, usually measured in terms of code coverage or functionality coverage.
2. A testing technique that divides the input values into equivalent partitions and selects test data from each partition.
3. A collection of test cases and test scenarios that are designed to test specific functionalities or features of a software product or system.
4. A sequence of test steps that represent a particular usage or workflow of a software application or system.
5. The data used to execute test cases and verify the behavior and correctness of a software application or system.
6. The process of retesting the modified or updated parts of a software application or system to ensure that no new defects have been introduced.
7. The process of running the test cases and test scenarios using the specified test data and recording the results.
8. A specific condition or set of conditions used to determine whether a software product or system is functioning correctly.
9. A detailed document that outlines the approach, objectives, and scope of testing for a particular software product.
10. A testing technique that focuses on testing the boundaries or limits of input values to uncover defects or errors.