You have been receiving daily builds from the developers. If fixes are either missing or not working, what type of testing is best suited for finding these issues?

Confirmation testing, often referred to as re-testing, is specifically designed to verify that defects reported in previous test cycles have been successfully fixed. When receiving daily builds from developers, changes frequently come with the introduction of fixes aimed at resolving known issues. Confirmation testing allows testers to focus directly on the previously identified problems to ensure that they are no longer present in the latest build. It involves executing the same test cases that initially uncovered the defects to check that the fixes worked as intended.

In the context of daily builds, if fixes are found to be missing or not functioning, confirmation testing is the most appropriate approach to validate the resolution of those specific issues. This allows for targeted scrutiny of the recent changes without getting bogged down by unrelated functionalities or broader aspects of the application that may not be directly related to the fixes.

While other types of testing such as regression testing also play a role in the testing lifecycle, they are broader in scope, ensuring that new changes have not adversely affected existing functionality across the application. Unit testing pertains mainly to individual components and would typically occur earlier in the development cycle, focusing on the correctness of localized code changes rather than checking for fixes in the context of the overall system. System testing evaluates the complete and integrated software product against specified requirements,