When a product owner discovers a new regulatory requirement, what type of tests will a tester typically run?

When a product owner becomes aware of a new regulatory requirement, the type of tests that a tester will typically run are change-related tests. These tests are specifically designed to validate that the changes made to the product—such as the implementation of new regulatory requirements—function as intended and do not negatively affect existing functionality.

Change-related tests focus on assessing the impact of modifications on the software. They ensure that the new requirements are integrated correctly and that they meet compliance without introducing new defects. This is crucial in a regulatory context, as failing to comply with new regulations can have serious implications for the software and its stakeholders.

While confirmation tests are intended to verify that specific defects have been fixed, regression tests are used to ensure that previously working features remain functional after changes are made. Functional tests assess whether the software behaves according to specified requirements, but change-related tests are more directly focused on the implications of new requirements and their effect on the existing system. Thus, in the context of a newly discovered regulatory requirement, change-related tests are the most appropriate choice.