It is unlikely that developers will have a better understanding of the requirements than testers, partly because testers work closely with the user community (and may be drawn from it) and partly because developers seldom work with the complete set of requirements in a medium to large development.

Testers may raise incidents related to the difference between user expectations and the specification, but these are not unnecessary. Such issues are more likely to arise at the later stages of testing.

Early testing (unit testing) is usually done most effectively by developers with a good understanding of the code and the development environment; they can be more efficient and more effective at this level. Later independent stages of testing offset any disadvantage from the lack of independence at unit testing level.

Non-functional testing is focused on testing the attributes of a system such as usability, reliability, maintainability, performance, and security. These attributes define how the system operates rather than what the system does. Non-functional testing ensures that the software meets certain criteria that are critical to its operational performance and user satisfaction​​.

The main purpose of use case testing is to identify defects in process flows related to the typical use of the system. Use case testing is a black-box test design technique that is based on use case scenarios. These scenarios help in validating that the system performs correctly for the specific ways in which the users will interact with it. This method is particularly effective in finding issues that users might encounter during real-world usage of the system. Reference: ISTQB CTFL Syllabus V4.0, Section 4.2.4​​.

Maintenance testing refers to the testing that is conducted on a software system that has been changed, either through corrections, enhancements, or other modifications. Its main purpose is to ensure that the changes have been implemented correctly and that the system as a whole continues to function as intended. This type of testing is crucial after a system has been released and needs to be updated or fixed. Maintenance testing ensures that the new changes do not adversely affect the existing functionality of the system​​.REREE33

The cost of fixing a fault increases as the software progresses through the development lifecycle. Fixing defects identified early in the requirements or design phases is less expensive compared to fixing those found later in testing or after the software has been deployed. This is due to the larger impact on the system, more extensive rework required, and potential disruptions to the user experience in later stages.

The Author is the only role that is typically used in a review.

A Champion might sponsor the review process but is not a defined role within an actual review; a Project Sponsor, if technically competent, might be asked to play a defined role within the review process, but whilst using that role they will not be a Project Sponsor; finally, a Custodian might ensure the results are stored safely but would not be involved in the actual review itself.

Static analysis of a software model is most likely to be performed by developers. This involves examining the code and software structure without executing the program, using tools to identify potential issues, such as coding standards violations, security vulnerabilities, and other quality issues. Developers often use static analysis as part of their development process to ensure code quality and maintainability. Reference: ISTQB CTFL Syllabus V4.0, Section 3.1.1​​.

Exploratory testing is used when it is unclear what the system is supposed to do. Therefore test execution tools are of little use because expected results cannot be predicted.

However, the record feature of a test execution tool can be used to log the actions performed so that defects can be recreated (option (A)) and rectified more easily.

The code of ethics for certified software testers includes considering the wider public interest in their actions for the public aspect, and advancing the integrity and reputation of their industry consistent with the public interest for the professional aspect. This ensures that testers uphold high standards of ethical conduct and professionalism, contributing positively to the public and the industry. Reference: ISTQB CTFL Syllabus V4.0, Code of Ethics Section​​.

Regression testing is designed to verify that recent code changes have not adversely affected existing functionality. It is particularly well-suited for test automation because automated tests can be rerun quickly and consistently. While regression tests are essential in many testing phases, they are distinct from acceptance testing, which focuses on validating that the system meets business requirements.