1										13
		2/11
																		14
3/10
					4
									5
					12
	6
							7
8
				9

Across

1. Retesting modified software parts to confirm no new defects were introduced after changes.

2. A detailed document that outlines the approach, objectives, and scope of testing for a particular software product.

3. The data used to execute test cases and verify the behavior and correctness of a software application or system.

4. An input value that falls within the specified acceptable range.

5. The extent to which software code or features have been exercised by tests, often quantified by coverage metrics.

6. The process of running the test cases and test scenarios using the specified test data and recording the results.

7. An input value that lies outside the specified acceptable range.

8. The table where each of the tests is recorded, including the data used, the expected outcome, and the actual outcome.

9. Testing input values at their limits to identify defects or errors caused by boundary conditions.

Down

10. A document that outlines the objectives, scope, approach, and resources required for testing a specific software product. It serves as a roadmap for the testing process and provides detailed information on how the testing will be conducted.

11. A specific condition or set of conditions used to determine whether a software product or system is functioning correctly.

12. A sequence of test steps that represent a particular usage or workflow of a software application or system.

13. A group of tests designed to verify specific functions or features of software or systems.

14. A testing method that groups input values with similar behavior and selects representative test cases from each group.

🖶