A change request is a formal proposal for an alteration to a product or system. During testing, a tester may identify issues that are not defects but represent a deviation from user expectations or a potential enhancement. Documenting and submitting these findings as a change request is a typical work product and output of a tester's activities. This information is valuable during the release process to decide on the final scope of the product.

A. Tested lest objects: This is likely a typo for "Tested test objects." The test object is the system under test itself; it is the subject of testing, not a documentary output produced by the tester.

B. Insulation recommendation: Assuming this is a typo for "Installation recommendation," these instructions are typically created by developers or a release management team. Testers verify these procedures but do not typically create them as a primary output.

C. Non-detected defects: This option is logically flawed. A tester cannot produce a list or document of defects that were not detected. A key output is a report on detected defects. While a tester provides a Test Summary Report that includes an assessment of residual risk (the risk of undetected defects), this is not the same as outputting the non-detected defects themselves.

1. ISO/IEC/IEEE 29119-3:2013, Software and systems engineering -- Software testing -- Part 3: Test documentation

Section 8.2.10, Change Request: This international standard, which heavily influences ISTQB, defines various test work products. While it doesn't explicitly list a Change Request as a test document, it's a standard project artifact that testing activities generate. Testers identify the need for change, which is then formalized. The output of the tester is the information that populates the change request.

2. ISTQB Certified Tester Foundation Level Syllabus 2018 (v3.1)

Section 5.2.3, Defect Reporting: The syllabus details the process of logging defects when a test fails. It states, "The objective of a defect report is to provide developers and other parties with sufficient information to identify the cause of the defect...". When a found issue is determined to be an enhancement or a change to requirements rather than a bug, the process often pivots to creating a change request instead of a defect report. This confirms that initiating such requests is part of the tester's role.

3. Kaner, C., Falk, J., & Nguyen, H. Q. (1999). Testing Computer Software. John Wiley & Sons.

Chapter 6, Reporting and Tracking Bugs: This foundational text discusses how testers report issues. It explains that not all reported issues are simple bugs; some are suggestions for improvement or point to flaws in the requirements. These often enter a change control system as change requests, making them a direct output of the testing effort.