QA Bug Report for CD Roller. Reported by:Joal C. Date: Nov 22, 2023. Build Version: CD Roller v10.61.30. Environment: Operating System: Windows 10 Pro 64-bit, x64-based processor. Processor: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (3.19 GHz). DVD Drive: Standard internal DVD drive (Dell desktop). Disc Type: DVD-R with 2.3 GB of data. Bug: Application crashes when trying to recover while DVD drive is scanning a disc. Severity: Critical. Description: When the DVD drive is actively scanning a disc in CD Roller version 10.61.30, Clicking the "recover selected" key or attepting to modify any setting causes the application to crash. The crash consistently occurs when clicking "Recover Selected" in the Data Recovery window while the scan is still in progress. The program closes immediately without displaying any error message, and any current session activity is lost. Steps to Reproduce: Launch CD Roller v10.61.30, insert a DVD-R into the DVD drive, allow the application to automatically begin scanning or indexing the disc, then while scanning is still in progress click "Recover Selected" Actual Result: The application freezes briefly and then crashes and closes without warning. Expected Result: Recovery should begin successfully without interrupting the scan or the application should display a message indicating that recovery cannot commence during an active scan; under no circumstances should the program crash. Reproducibility: The issue is 100 percent reproducible and occurs consistently during testing. Preliminary Analysis: The issue appears to be related to a thread synchronization or shared resource conflict between the background disc scanning process and the recovery startup process possibly due to recovery modifying or reinitializing resources currently in use by the scanning thread, leading to an unhandled exception and termination of the application. Impact: This issue causes loss of user progress, interrupts disc scanning, may risk temporary file corruption, and significantly affects overall application stability.

I would go through the features of the product and use every one in a "normal" way to gain an idea of how the product is supposed to work naturally (unless previously provided a template of the products functionality). I'd then stress test the product through either loading it with tasks and or in conjunction with other programs that may lead to any bugs showing themselves. Lastly Id on an in depth and individual basis go through all process of each feature to ensure 100% functionality. In the event of any bugs or issues id take a screenshot or screen recording (if applicable), make a detailed written report of what happened, what actions i took that led to discovering the bug and report all of my findings to the apropriate channels.